Re: RequestContext Overhead

Each RequestContext will have an implementing class generated, so yes, there's an overhead (class metadata, initialization code, etc.)

The overhead is much lower as with RPC though (as much more code is shared between contexts than between RPC services).

Just a reminder though: premature optimization is the root of all evil (http://en.wikipedia.org/wiki/Program_optimization#When_to_optimize)

...and the GWT compiler improves from version to version so that the overhead becomes lower over time (so you don't even have to think about it, until you *have* to think about it (i.e. you have a perf issue, and you identified through benchmarks and other perf analysis that it's a bottleneck))

Compare that overhead with the reduced readability (thus less maintainable code) of a giant RequestContext, and particularly its server-side counter part service, with dozens of methods!

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/GGpaW2WC55IJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.