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.
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. Dan On Fri, Jun 11, 2010 at 3:02 PM, <[email protected]> wrote: > Since the underlying implementation is so different, maybe we should > break any users of this and instead introduce something that is less > fragile, like a class using only translatable primitives that can > serialize/deserialize itself. > > > > http://gwt-code-reviews.appspot.com/604801/show > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
