On Tue, Sep 16, 2008 at 10:10 AM, Thomas Broyer <[EMAIL PROTECTED]> wrote: > > > On 15 sep, 20:53, "Jim Freeze" <[EMAIL PROTECTED]> wrote: >> >> JSON can be made as fast and json libraries for python already exist. >> So, I seriously doubt anyone is writing JSON serialization from scratch. >> Your server side code probably only needs to be modified with >> self.data.to_json. > > ...but if your client needs to send JSON, you need a JSON-serializer > (which hopefully GWT provides you, but not the most performant, as it > relies on JSONValue wrappers for each and every single thing you'll > want to serialize (or parse, as it works both ways). > com.google.gwt.json.JSON is unfortunately hard to use and generates a > lot of overhead.
[elided] > (I you ask me my opinion: GWT-RPC is not RESTful so I don't use it, > but the hability to share a class between client and server code is > appealing; I'm not using such a thing either though) You answered for me. :) Yes, when using REST, json is only from server to client. Never the other way. What that means in reality, is that I don't have a client side algorithm that generates a massive amount of data change that needs to be marshalled back to the server. Usually changes are from the user. -- Jim Freeze --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
