The strength of GWT-RPC is that it allows for near seamless communication between the GWT Client and a Java based Server. GWT-RPC on the server is pure java and allows for easy hooks into Hibernate and other Java based server technologies. If your server isn't Java based, then JSON is the best way to go...
On Oct 29, 6:37 am, Brian <[EMAIL PROTECTED]> wrote: > I haven't touched gwt rpc, as it just seems using requestbuilder and > shoving json across the wire is straightforward. > What's the compelling case to use gwt rpc? Remember, I haven't even > looked at the docs. I'm not trying to bash anything here, just > wondering why it's worth it to setup gwt rpc vs just moving json > around. My backend server is tomcat. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
