Wednesday, July 13, 2016

Re: GWT RPC in GWT 3.0+

Will the gwt serialization mechanism used in GWT-RPC remain? GWT object serialization has been plugged into the atmosphere (realtime communication/websockets) GWT extension. It would be useful to know if we should migrate away from the GWT serialization and towards JSON.

On Thursday, July 7, 2016 at 3:53:18 AM UTC-7, Thomas Broyer wrote:

On Thursday, July 7, 2016 at 11:54:11 AM UTC+2, Philippe Gonze wrote:
Totally agree. GWT 3.0 without RPC would be GWT 3.dead for many of the current GWT developpers,

For me GWT is "Web development based on Java expertise, with practically no other technology implications". Extremely powerful and pleasant. Seems that GWT 3.0 is announced as "no more GWT":

From "GWT's mission is to radically improve the web experience for users by enabling developers to use existing Java tools to build no-compromise AJAX for any modern browser."
Also pay attention to what GWT is NOT about.
GWT 3.0 as described in this thread would still follow this mission statement.
Providing tools to do RPC, even if differently than today, would still follow the design axioms. But RPC in itself is about making compromises on AJAX use ("obscure" payload, asymmetrical payload because they were not meant to be parsed by the same tools and in the same environments, everything sent to the URLs, etc. all of this make it impractical at best to use RPC along with, for example, service workers), and that will eventually degrade the web experience for users. Moving away from RPC is actually trading development "convenience" for a better user experience.
Our plan will probably to stay with 2.8...

And this is exactly why GWT 2.x and GWT 3 are expected to coexist for a while.

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
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment