We have a web server proxy before the app servers (GWT client code is
served from this web server and not from the app server). On the app server
we can deploy as many versions as we want and on the web server proxy we
configure which customer should access which deployed version. So basically
I'd like to pick up this topic again after 2 years, what an interval!
My general concern is that during the deployment refreshing the page
wouldn't solve the RPC break problem. As long as we have a mix of old and
new server during deployment and no measure to ensure that the new clients
only
Seems the topics are ranked by post date by default, this is the link to
the old topic I'd like to bring to people's attention again.
https://groups.google.com/d/msg/google-web-toolkit/-p5wr04A-eg/cmxBYlwYhrYJ
Basically I hit the rpc outage problem during deployment I wonder how to
solve it.
*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.*
*
*
*re. Old Client, New Server*
I prefer to take a different
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
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
