I'm pretty sure JSON is going to be faster because of the unmarshalling speed on the client. There is nothing to prevent mixing the models a bit. XML sent to the server (probably most efficient for Java to demarshal using stax), and JSON sent in response to the client. On the server, custom unmarshalling is probably always going to beat a generic reflection-based de-marshaller.
It all depends on how much of a "main concern" speed really is. With respect to the client, you won't beat JSON for unmarshalling -- it's a straight eval() basically. On the server, there are various options that range from zero-effort/mediocre-performance to high-effort/high- performance. XML/StAX is probably between those two extremes. On Aug 5, 11:53 am, asianCoolz <[email protected]> wrote: > if speed is the main concern, should i choose to use json for data > interchange with server compared with RPC call and XML? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
