Stop browser scripts caching in GWT App -
I have a GWT app deployed on our client's machines as well as ongoing development, Revised versions have to be released periodically. Every time we issue a new version, we often run into problems where the client's browser has cached the old script scripts and behaves this awkwardly for a while because the data is trying to work on it He is not quite compatible with him. What is the best way to overcome this problem? At present, I have to tell users to clear their browser's cache for a new release, but it would be good if they do not have to do this.
By default, the bulk of your app should be cached by the browser unless its new version is Be Generated by Your Build Process
The GWT can help to understand the bootstrapping model to understand how it works.
Your client request is not cached, your-app-name .nocache.js
, and it does nothing except the browser's user agent and capabilities, and related apps The second request for the JS
At this point, the script should be cached by this request browser if it has been previously requested. This is a {indistinguesable-numbers-and-letters} .cache.html
file.
When you revise your app, the nocache.js
file will be executed and will ask for a separate cache.html
file from the server, which Will not be present in the cache, but after downloading it will be cached by the browser.
Are you doing something abnormal with deferred binding or caching headers on your server? This could potentially cause your nocache.js
file to cache, which will request the old cache.html
s from the browser's cache.
Comments
Post a Comment