Ok - I'm going to work with the request builder for now and see how
that goes. Really my only issue at this point is the slow RPC
transfer.
On the client side, the data is parsed into a structure upon receipt,
consisting of several different kinds of HashMaps and ArrayLists of a
few basic object
On Oct 13, 4:04 pm, "Dean S. Jones" <[EMAIL PROTECTED]> wrote:
> A bit of advice from lessons on my last project: Reduce your in-memory
> footprint of data to "only what you must have to display
> what is needed to the user at the time",... (except for cacheing
> frequently used data). Several h
On Oct 13, 9:13 am, rakesh wagh <[EMAIL PROTECTED]> wrote:
> > 3. Is there another way all together that I could approach this to get
> > the data to the client faster?
>
> For this specific scenario use RequestBuilder on client and a
> traditional servlet on the server.
I'm reading up on requ
On Oct 12, 9:50 am, gregor <[EMAIL PROTECTED]> wrote:
> RPC involves trade offs between minimizing the number of calls against
> individual call payload size. If you explained a bit more about what
> all this data was and what the client does with it, you may get some
> good ideas for how best
Greetings,
I am still relatively new to GWT, although I've been tinkering with it
for about a year now. I've been working on some small network
troubleshooting tools and as part of the process, I'd like to pass
configuration files from server to client (which are then acted upon
by the client sid
