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
My general observation is that ANY non-trivial data processing in 2+
orders
of magnitude faster on the Server than on the Client ( Especially with
IE )
If all the data really is needed in the client, I would rather
"structure/parse" it
on the server and send something like JSON over the wire. Band
Hi Matt,
As Dean says, RequestBuilder would return the string much faster.
However I would be worried that trying to do the sort of queries you
mentioned against raw text data would also be slow, or building some
complex data structures from it client side against which to run them
may be a) slow
If it's really just plain text, then RequestBuilder with a plain
Servlet will be much faster.
You avoid the Machinery of RPC. It may be you should then look into
GZIP compression
on the wire... there are several Servlet Filter packages out there as
an example. GWT by
default uses GZIP if the paylo
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
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 hundred K of information is likely
not useful to the client. i.e. showing
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
> 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.
--~--~-~--~~~---~--~~
You received this message because you ar
Hi Matt,
I've just checked an example XML file I have to hand (standardjbosscmp-
jdbc.xml) which is 115k. This comprises about 50 screen-fulls of XML
data. I think that probably qualifies as an excessive payload for a
single GWT RPC call. I suspect the reason it's slow is because the
alternatives
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
11 matches
Mail list logo
