Hi Sri, Thanks for the reply.
> *IMHO, once you have deployed new code, you want to tell the users to > refresh the browsers as soon as possible. Trying to get old clients working > with new code can work at times; but since there is no guarantee I prefer to > fail-fast.* I think it depends. I am hoping to get to a point where I can deploy bug fixes mid-day and not worry about users that are already in the application losing their work and having to refresh. Assuming the RPC contract is 90-100% the same, this seems reasonable. Though it does mean users will continue using out-of-date client code instead of the latest and greatest, with potentially important bug fixes. I'll think about that. > So, I end up overriding doGetSerializationPolicy() in my RPC Servlet. If > super.doGetSerializationPolicy() returns null, I throw an > IncompatibleRemoteServiceException. The client code handles this exception > and asks the user to reload the browser. Interesting. Thanks for the mentioning that--I'll keep that in mind. > *re. New Client, Old Server* > In this case, client code will get a 404 when trying to load > <permutation>.cache.html file. It is possible to detect this and take > action. You need to provide an implementation of onLoadErrorFn Nice, thanks for the link. I'll check it out. - 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.
