On Fri, Jun 11, 2010 at 3:07 PM, Daniel Rice (דניאל רייס) <[email protected]>wrote:
> Right now, the standard RPC format hasn't changed (although deRPC has, > since the whole point if to be able to eval the payload into the client). > So anyone who has a custom RPC system needs a way to generate a double[2] > from a long. Ok. > Longer term, I'd like to transmit longs as an int[3] instead, in which > case I would agree that it would be good to insulate subclassers from the > details of the wire format. > Since it is actually going to be transmitted as ASCII characters anyway, I am not sure it is better than just sending the string representation of the long and processing it normally rather than parsing multiple values. Especially currently where the work to parse two doubles and convert them to 3 ints seems far more than just doing the straight parse anyway, and it also makes the server-side much simpler. -- John A. Tamplin Software Engineer (GWT), Google -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
