I am building a Web application using GWT on top of a python django server.
I've been busting my butt to be able to interface the two cleanly. My goal is to be able to define two-line services in a django views file such as this: def service_get_male_users(request): return gwt_response(User.objects.order_by(age).filter(gender='M')) Then I want to be able to run the command python manage.py sync-gwt ...which I wrote, and have it generate the Service, ServiceAsync, onRequest() and onFailure() (the typical RPC plumbing) code in GWT for all the functions prefixed 'service.' I would also generate JavaScriptOverlays that mimic the django models these functions use (such as User) to easily access these data types in Java. All I would have to do is 'fill in the blank' in my Java code for handling these service callbacks, with all this plumbing and these overlays at my disposal. This was all fine and dandy, until the problem of serializaling JSON objects to encode and decode both in python AND java became an issue. I have no networking background, so this is all new to me, and my project has been stalled for a while because of this, so I'm wondering... What is the big advantage of using GWT RPC over Request Builder [http://code.google.com/docreader/#p=google-web-toolkit- doc-1-5&s=google-web-toolkit-doc-1-5&t=GettingStartedJSON] or simply JSON via HTTP [http://code.google.com/docreader/#p=google-web-toolkit- doc-1-5&s=google-web-toolkit-doc-1-5&t=GettingStartedJSON]? I'm generating all the code anyways, so why not generating something simpler than RPC? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
