I'm trying to transmit large amounts of data from my server to my
client using the Asynchronous RPC calls. I've noticed that for these
arrays often take quite a long period of time to transmit. I'm only
sending four sets of data, but containing several hundred (to perhaps
a thousand) points each. I'm transmitting a simple class that holds
four parallel double arrays that will be used to populate a DataTable
for a visualization (from the Google Visualization API).

I could restructure my classes and doubtless get a little speed up (by
only having one array that I am transferring), but the entire
transmission process occurs three to four times faster if I parse the
data on the server from a byte array to a string using a string
buffer, than transmit a single string across the RPC.

I've seen that I could manually code the serialing interface for the
RPC call, but, unless I can find a way to send a large blob of data
and escape the arrays, I don't think that will speed up the process
too much.

I been looking into the JSON queries, but am not sure how much faster
they could be since it seems the point of that is to transmit a long
string across as well. As I understand it, the parsing would be faster
because JavaScript natively reads it.

Finally, I've glanced over HTTP requests, but I'm not sure about speed
gains there either, and I don't want to have to entirely retool my
server.

My question is thus: I'm fairly inexperienced at web development and
these sorts of client/server interactions. What would be the best way
to encode this data for quick transmission to the client?

Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to