On Monday, October 6, 2014 10:25:24 AM UTC+2, Jens wrote: > > I'm trying to hook into the >> failure of when a client loads the .nocache.js from one version, >> but tries to get the permutation from another. >> > > Hm interesting, we never run into this. How do you update your app? Maybe > we also suffer this small window but never noticed it. We deploy a second > app on app servers and once that is done we tell load balancers to redirect > to the new app. Now a couple of things can happen: > > - User is logged in and has all split points => GWT-RPC Exception might > occur => app reloads > - User is logged in and tries to download old split point (404) => Caught > on split point level and app reloads > - User is not logged in => user will load new nocache.js file and gets new > app >
- User starts loading old nocache.js, you tell load balancers to redirect to the new app, the nocache.js runs and tries to load an old permutation from a new server where it doesn't exist. I suppose Stephen's deployment strategy is different, with some servers still serving the old app while others already serve the new app, and the load balancer could direct traffic to either server; but the end result is the same. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/a1ca5767-e08e-4874-aeb6-fd6f7ef73b19%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
