On Thu, Jul 15, 2010 at 6:19 PM, Ray Cromwell <[email protected]>wrote:
> It's not about parsing, it's about having a shared interface, so if I
> write a method, say double sum(JsonArray arr) {} it can run as shared
> code, either compiled on the client, or run in the server. The current
> dichotomy of having a separate Json object model on the server and
> client prevents this. I faced this problem in my user libraries
> before, where I had shared code for processing numerical json
> datasets, and ended up having to write my owned shared json library
> interfaces to make it run on client and server.
>
If you are using JSOs, I don't see how you run that on the server anyway. I
suppose you could have a SingleJsoImpl interface, and then dynamically
generate bytecode for an implementation on the server -- is that what you
are asking for? Even in that case, it is dirty in that your JSO classes
have to be visible when building the server code.
--
John A. Tamplin
Software Engineer (GWT), Google
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
