> > 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 -- J. -- 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/4607c79c-5677-45fd-a48e-7ddb2cac0c5a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
