> > I see in repeated cases, where someone's browser displays old app design, > and clearing browser cache brings up the latest. How can that be?
A few things can go wrong - 1. Browser is caching <module>.nocache.js. If this happens, the browser will also download the stale *.cache.html files. And, you if you have made changes to RPC services, this will manifest itself as IncompatibleRemoteServiceException. 2. Browser is caching css/html/images, so even if your code is new, the look-and-feel will be old. As I mentioned earlier, the problem is best mitigated by getting rid of the third "Cache for Sometime" bucket by making aggressive use of ClientBundle. --Sri On 8 July 2010 07:39, bhomass <[email protected]> wrote: > I don't understand something. according to you, none of the generated > js would fall under "cache for sometimes". That means all the js files > except nocache.js would be cached forever. and GWT takes care that new > file names will be generated when this type filed change. By this > logic, there could never be any stale js problem. yet, I see in > repeated cases, where someone's browser displays old app design, and > clearing browser cache brings up the latest. How can that be? > > On Jun 26, 6:44 pm, André Severo Meira <[email protected]> wrote: > > Nice! > > > > 2010/6/26 bhomass <[email protected]> > > > > > do you mean to set a limited cache lifetime or to not cache at all? > > > > > I do normally want the javascript files to be cached for performance > > > purposes. > > > > > On Jun 17, 10:02 pm, Sripathi Krishnan <[email protected]> > > > wrote: > > > > No, you can't do that. But if you set appropriate cache headers, > there is > > > > never a need to delete old files. > > > > > > --Sri > > > > > > On 18 June 2010 06:10, bhomass <[email protected]> wrote: > > > > > > > is there any way to programmatically get user browser to delete all > > > > > its cached javascript files in order to push down new ones? > > > > > > > -- > > > > > 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]<google-web-toolkit%[email protected]> > <google-web-toolkit%[email protected]<google-web-toolkit%[email protected]> > > > > > <google-web-toolkit%[email protected]<google-web-toolkit%[email protected]> > <google-web-toolkit%[email protected]<google-web-toolkit%[email protected]> > > > > > > > > > . > > > > > For more options, visit this group at > > > > >http://groups.google.com/group/google-web-toolkit?hl=en. > > > > > -- > > > 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]<google-web-toolkit%[email protected]> > <google-web-toolkit%[email protected]<google-web-toolkit%[email protected]> > > > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/google-web-toolkit?hl=en. > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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.
