We are trying to resolve a caching issue we are having when we deploy
our GWT app.  Currently our servers don't really set any cache control
headers, not even expires.

I've only seen one opinion on this issue - they say to set cache-
control headers for the host page and nocache.js files to no-cache
(http://seewah.blogspot.com/2009/02/gwt-tips-2-nocachejs-getting-
cached-in.html).

Our GWT app really lives in one .html file - the host page, so if
someone were using the app when we deployed a new WAR their browser
wouldn't really know it.  To me it seems that we'd want to have
clients cache for at least a while?

Is there a best practice on this?

--

You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.


Reply via email to