[EMAIL PROTECTED] schrieb: > 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.
I was going to answer more or less the same, so I build my answer on top of yours ;-) The "sexiness" comes with the implementation of RMI with the specifics of being forced to perform asynchronous requests. So the only thing you have to do is call a method that is defined in an interface, leading to the call of the correspon- ding method being implemented in the servlet. How the parameters passed to the method are marshalled/un- marshalled is done by the RPC-framework, the same is valid for the data being returned by the method. It makes testing the implemented methods in the servlet easier as well (as long as you don't access the request- and/or response-instance directly) by allowing you to call an explicit method instead of firing up a HTTP- server, create an HTTP-request and send that to the server or use httpunit for establishing a virtual Servlet- environment to pass in the request that way. > If your server isn't Java > based, then JSON is the best way to go... ACK Regards, Lothar --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
