Well, server-side code, the RPC implementations, are just normal java servlets so you should be able to do anything your servlet container allows you to do.
> (I can't > test this code right now because the Google App Engine plugin on the > Mac doesn't seem to run hosted mode correctly). On the other hand, the google app engine only allows to use a subset of java 6 so it's possible that your code example won't work without modifications. You can use GWT and GEP without the app engine though so you CAN test the code (just remove the app engine sdk from your project). Cheers, Salvador On Apr 23, 3:59 am, JavaJosh <[email protected]> wrote: > Hello, > > I actually rather like the GWT RPC API and was hoping to use it for > more than client/server communication - in fact, I want to use it for > server/server communication. Here is some example servlet code: > > http://gist.github.com/100232 > > The callService() method would be designed to hit a different server, > of course. > > > BTW the attributes of GWT RPC that I like is the JSON transport, and > the asynchronous API. I also like the idea of dealing with > communications in a more homogeneous way. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
