And to follow up Suri's excellent description, I "think" it uses plain old port 80, but it is definitely just HTTP. You are just using a browser. If you want to be certain, fire up Wireshark (if you don't have this tool on your machine, shame on you!) and watch on port 80. Now that I'm typing it, I think you can configure Tomcat to use most any port. I think we were using 8080 for a while. But the bottom line is that it is just plain old HTTP.
Later, Shaffer On Dec 7, 4:12 pm, Suri <[EMAIL PROTECTED]> wrote: > Hi Venu, > My understanding is that RPC is really a layer above the HTTP and if > you notice how it works, its not unlike another servlet call. The > serialization/deserialization has been abstracted to make life easier > for us. So, to answer your question, yes, it is communicating over > HTTP from where your webserver will pass it over to the servlet > container just like another servlet call. Hope that helps > > Suri > > On Dec 7, 7:09 am, Venu <[EMAIL PROTECTED]> wrote: > > > Hi grp, > > > What port does GWT RPC mechanism use? Is it communicating over HTTP? > > If not, what port does it use? > > > Thx --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
