Friday, January 2, 2015

Re: GWT 2.7 manifest support

Has this something to do with this issue?
https://gwt-review.googlesource.com/#/c/10520/
(more infos here: https://groups.google.com/forum/#!topic/google-web-toolkit-contributors/q4BgTzs6PXw)

I am not so deep in this topic.

Could be if the timestamp is always the same (the one of the *gwt.xml file) then your web server might think that the file has not been changed. If your web server has correct caching headers for *.nocache.* then any cache first asks your web server if zzz.nocache.js is stale and if not then the cache might return an older, already cached version.

To test it you can either use GWT trunk or just change the timestamp of your zzz.nocache.js file by editing it.

-- J.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment