Hi, I've done some research about keeping GWT deployments as seamless as possible for both new and old clients.
Basically avoiding (when possible) the LegacySerializationPolicy, IncompatibleRemoteServiceException, type name elision, no RPC whitelist, etc. errors that I had been seeing while deploying upgrade to a gwt app. I had trouble finding an existing writeup that covered everything, so I wrote up a more detailed description at: http://www.draconianoverlord.com/2010/07/07/gwt-seamless-upgrades.html It seems to boil down to: * Use IsSerializable and no type name elision in the RPC DTOs (can't rely on serialization policy file being available) * Handle IncompatibleRemoteServiceException in the RPC AsyncCallbacks for when the contract has actually changed * Handle 404’s in the runAsync onFailures * Minimize/eliminate the window when both old and new servers are available I'd appreciate it anyone could verify/correct/add to my list of suggestions. When in doubt, I can deploy at night, but I was hoping to gain some flexibility and just wanted to see what it would take to make it possible. Thanks, Stephen -- 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.
