Problem with Client Caching

[Niels_EMP]

Hi

I currently have the problem that when I deploy a new version of my app to production I have to ask users to hit Ctrl+F5 to force a cache update. If I don't do this users that are logged in while the versions are updated are seeing a mix of new and old SGWT generated JS and CSS.

I'm thinking that it'd be an idea to save a version cookie on the user's machine and the check up against this in my sessionmanager to force an update.

Is there a recommended way to do this automatically and maybe even transparent to the user?

[Blama]

Hi Niels_EMP,

doesn't an undeploy/deploy-cycle kill the user sessions for you and forward the user to the login page (Assuming you are using jsecurity-authentication)?.

For me it does using Tomcat 7 (also for Tomcat restart). Afterwards the users will automatically pick up the new *.nocache.js.

Best regards,
Blama

[Isomorphic]

A more typical solution is to deploy each version at a different base URL so that caching is never an issue.