the idea seems fine but please keep an eye on the resulting size of
JS :)
On 24. Feb, 23:28 h., John LaBanca jlaba...@google.com wrote:
GWT Contributors -
I drafted a proposal for a new pattern that the GWT team will use to replace
existing GWT widgets with newer, shinier widgets. The
All necessary information is comming in the RPC call. If you take a
look into RemoteContextSerializationPolicy you can see how the HTTP
connection is initiated. You don't have to take care about where are
RPCs located because the call itself will tell you.
The drawback of remote context is that
well, you may have as many client contexts as you wish. In local
context configuration you need to copy RPC files to the server - and
that is what you apparently don't want. But in remote context these
RPC files are generated on the client (by ProxyCreator), they remain
there and server is able to
Hi Ed,
maybe this will give you some relevant answers:
http://code.google.com/p/acris/wiki/SeparateClientAndServer ,
especially the part Accessing RPC files from server. There is a
solution how to access RPC files in no-server mode remotely also.
On 22. Feb, 11:17 h., Ed post2edb...@hotmail.com
Hello everyone,
I would like to collect information about efforts to build a binding
solution for GWT and hopefully to synchronize with others. We have
(and are still) developed binding solution between visual
representation and data providing layer. If you are interested, please
follow us at:
