Re: Best practices for reducing generated RPC Serialization code?

The thing that seems to have the biggest impact: be very specific about concrete classes, otherwise you get an explosion on the number of serializers that are generated. So don't use List, Collection, Iterable, Map or even worse Serializable. When using generics also try to have a specific base type in the generic parameter declaration or the compile size explodes.

As a Java dev we have been trained to use Collection interfaces or after Guava even going to Iterable ... not a great idea with RPC.

So I am using a small set of final collection classes in the member declarations (but not on the setters/getters).

I'm also using a command pattern iso RPC directly, that makes my exposure to GWT specifics minimal and I can bypass the RPC part for automated tests. This way I add extra features like bulking, security, caching, etc.

On Mon, Jun 2, 2014 at 10:52 AM, Ed <post2edbras@gmail.com> wrote:

What are the best practices for reducing generated RPC Serialization code?

Currently I use small Remote backend interfaces such that the serialization code is only downloaded when used in a split point.

However, reading this SO post, I get the impression it's better to use one big backend remote interface?

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

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