Maybe keeping the old *.gwt.rpc files around (provided you didn't change the remote service interfaces and transported types), or maybe it was a feature of the abandoned deRPC (ever noticed that Google Groups –which uses GWT-RPC– regularly asks you to reload the page to get the newer version? (luch more likely to happen if you keep your browser/tab open for days)).
For runAsync, keeping the old fragments will do it (obviously, the users will still be running the old version, so your server should be prepared to handle calls from this version). Unless you're deploying several times a day, it's much easier to just have users reload the app: only a few users should ever notice it, and most likely when coming back to the app after they let it open in their browser during the night/lunch (of course plan your deployment depending on your app's traffic) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/mT982Bb9d3wJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
