I agree that it looks like the overhead is per-requestcontext. This is
also reflected in the size of the abstract request factory vs the
abstract request context.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send
On Tuesday, August 30, 2011 6:52:57 PM UTC+2, John Maitland wrote:
>
> Thanks Thomas. And the code sharing between request contexts is done
> at the RequestFactory level or between request factories. For example,
> if I have a entity proxy that is used on multiple request factories
> would tha
Thanks Thomas. And the code sharing between request contexts is done
at the RequestFactory level or between request factories. For example,
if I have a entity proxy that is used on multiple request factories
would that be shared? This is important if you wanted to code split an
entire request facto
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 optimiz
Is there a overhead to having multiple RequestContexts inside a
RequestFactory? I know with RPC, there was a overhead of having
multiple async services.
John
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send emai
