On Friday, September 16, 2011 12:00:59 PM UTC+2, Thomas Broyer wrote: > > *.cache.* and *.nocache.* are just naming conventions adopted by GWT to > help setup the "perfect > caching"<http://code.google.com/webtoolkit/doc/latest/DevGuideCompilingAndDebugging.html#perfect_caching>configurations.
Really useful insights! > > If you enable caching for the *.nocache.js file, then you explicitly allow > intermediate servers/proxies, and browsers, to serve/use a possibly obsolete > version of you app, without necessarily checking for a fresher on at your > server. That means your servlets have to be prepared receiving requests from > such versions even after you pushed an update to your server. > That's also what I had in mind. I just wondered why so many Google apps use the *.cache.js version. Ok, if the content ist pretty static and for a *very high* number of reqs/s it may be a viable solution. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/3LfdY32RvbwJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
