http://code.google.com/webtoolkit/tutorials/1.5/RPC.html claims "The GWT RPC framework makes it easy for the client and server components of your web application to exchange Java objects over HTTP. The server-side code that gets invoked from the client is often referred to as a service. The implementation of a GWT RPC service is based on the well-known Java servlet architecture."
Being that that service is a servlet there's no reason why one shouldn't use an access to a db, a call to a webservice or whatever permitted by a servlet itself. I'm doing a browser -> (gwt) servlet -> webservice. I don't care about the rpc communication between the browser and the server, the webservice can take much time to answer, and being the call asynchronous it's all ok: when the method returns the callback on javascript will be executed. On Mar 18, 5:18 pm, tetsuo <[email protected]> wrote: > you bedder consider the differences between a remote control and a > webservice interface > > >http://en.wikipedia.org/wiki/Webservice > >http://en.wikipedia.org/wiki/Remote_procedure_call > > the rpc is like the controller for your tv, the webservice is the like > two tv´s communicating to each other. in your example you want to > control your tv with a tv - that dosnt work. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
