> Scenario: A user is running version n-1 of a gwt app. Meanwhile, > version n is deployed. I assume the client will get RPC serialization > exceptions. The user gets frustrated. > > What's the best way to address this?
If you use IsSerializable (and no type name elision), and don't have any actual API changes, you'll be okay, you user shouldn't notice. Otherwise you'll have to catch IncompatibleRemoteServiceException and ask your user to reload the app. I was mulling over this scenario awhile ago and wrote a blog post about it: http://www.draconianoverlord.com/2010/07/07/gwt-seamless-upgrades.html - 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 google-web-tool...@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.
