I would change your caching settings to use no-cache or must- revalidate. If you have a normal release schedule then you can use a very short Expires date or small Cache-Control: max-age time and base that on your next release.
Otherwise, if your release schedule is more erratic, I would just leave off the Expires and max-age headers and use must-revalidate or no-cache for files that are getting changed every release. As long as you're sending an ETag and/or a Last-Modified header for each request then your requests should still be cacheable but their browser should be checking to see if the files have been modified every single time. It's a bit less efficient than the browser being able to skip that step and just use the cached data without even pinging the server, but it beats having to tell your users to clear their cache. Sometimes a hard refresh (e.g. Ctrl + Shift + R in Firefox) is enough and you don't have to clear the cache, but that depends on the browser. As for GWT-specific ways to make that happen, I've just started using GWT so I'm sure there are other people here who will be able to help steer you in how to make all that happen with GWT. On Aug 4, 11:19 am, shahid <[email protected]> wrote: > I have a GWT app deployed onto our client's machines. As an ongoing > development alongside, we have to release new improved versions of the > application fron time to time. Everytime we release a new version we > often run into the problem where the client's browser has cached the > old scripts scriptsand for a while it behaves strangly as the data it > is trying to work with is not quite compatible with it. What is the > best way to overcome this problem. Currently I have to tell the users > to clear their browser's cache for a new release but it would be nice > they don't have to do 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 [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.
