Re: GWT Material Design

There are ways to overcome this.

The blunt way, custom field serializers for all of the data models. 

The other solution, replace the usage of the serialization policy by overriding the remote servlet base implementation and using some other serialization, but still utilizing the RPC mechanisms.

On Sunday, March 29, 2015 at 6:47:53 AM UTC-7, Andrei wrote:

RPC is not a good idea for mobile apps. Every change in your code may result in an incompatible serialization policy. This is not a problem for regular web apps - a user can load a new version by simply refreshing a page. It's more of an issue if an app is installed on a mobile device - not all users will update their apps at the same time, so you will have to run multiple versions in parallel to keep serialization policies in sync. A better option is to use a REST API which can often be extended without a need for a mandatory update of all clients.

On Saturday, March 28, 2015 at 4:29:33 PM UTC-4, mark kevin ringor wrote:

GWT Phonegap also is added in the repository. You can check it out and play with as Im studying the RPC mechanism of GWT inside phonegap.

--
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.