If you use GWT-RPC then you have to live with page reloads. We use GWT-RPC and the only downtime we have is when updating the DB schema. In all other cases the user gets a "App has been updated and will be reloaded now" message and the app reloads itself.
-- I am not sure which security issues you would have but technically you could make an "allow everything" serialization policy on the server. That way GWT won't throw exceptions if serializable classes have changed and thus the serialization policy file changed. However GWT will still throw an exception when updating GWT itself and the GWT-RPC version is different between client and server.
If you don't want all of the above then don't use GWT-RPC.
-- J.
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.
No comments:
Post a Comment