Hi, when I install a new server version, I redirect my URL to a "under construction" page beforehand. Then I undeploy the app and redeploy it.
However, during this process the clients often still have the old app in their browsers. When the new app is deployed they may receive "incompatible" errors. When the new app is still not deployed, they receive "not available" errors. In both cases, a browser reload will help, either by serving the new app or by serving the "under construction" page. My problem is that even if I do the redirect, the clients do not see the "under construction" page, because the app is still in the browsers and struggles with errors. Is there a mechanism, so that the apps in the browsers inform the user that a reload is required when a) the app is not available or b) the server's app is newer than the browser's version? Or how do you deal with this problem? Thanks Magnus -- 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.
