Re: Continuous Delivery with GWT

Shame no replies. I was looking forward to the answers.

My guess was that you would have to keep each version of the server side running until no clients were using it any more... So route the request to the correct version of the code... Maybe a webapp per version? Level of pain depending on how you do your middle tier?

Off topic but have you looked at RequestFactory? Depends what you are doing but if you are doing lots of forms etc it is really slick.

 

On Monday, August 11, 2014 8:59:31 PM UTC+1, Tony BenBrahim wrote:

Has anyone successfully implemented Continuous Delivery with GWT. The biggest obstacle I see is GWT RPC, that seems to check that the client version matches the server version, so that when a new version of a backend is deployed, users will get an error message about an incorrect version and be asked to refresh the browser. I will look at disabling this check, but if it is not possible or has negative consequences, may have to switch to REST+JSON from GWT RPC? Anyone tried this successfully?

Thanks in advance

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.