Tuesday, September 15, 2015

Re: How to support new version and old version like Google Inbox?

Take a look at HTML5 appcache: http://www.html5rocks.com/en/tutorials/appcache/beginner/
And the great library for GWT: http://realityforge.org/gwt-appcache/


On 15/09/15 10:30, Shawn Johnson wrote:
I'd like to have smoother updates to our GWT application, and not break client's that are actively on the site.  We are using GWT 2.7, RPC, and code splitting features.  I'd like to give users an experience similar to Google's Inbox (GWT) application - where a nice, non-intrusive notification appears notifying the user of a new version of the application - and allows them to reload when they get to a good point.  Currently we see errors in the logs after a deployment, indicating users' client application is attempting to make an RPC call to an outdated endpoint, or trying to load a .js fragment (code-split) that no longer exists.  I'd almost like to see a versioning of the relevant parts, so maybe the build process and linkers(?) might be more version aware.  

Something like:


Any thoughts or ideas?

You received this message because you are subscribed to the Google Groups "GWT Users" 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.

No comments:

Post a Comment