Actually most containers pool their processor threads in order to conserve and regulate resources.
The RemoteServiceServlet in GWT simply decodes the response and invokes the method which the request relates to. Theres no magic or rocket science going on here. I don't know what tests you've run, but they're obviously giving you some skew results. That said, a single browser will generally only allow 2 concurrent connections to the server. If your tests ran in your browser, what you're likely seeing is this limitation. Hope that helps a bit. Take a look at the RemoteServiceServlet and RPC code to see how it works otherwise. [email protected] wrote: > I never said it cretaed multiple instances, simply a new thread per > request. > > On Jan 23, 4:30 pm, Shawn Pearce <[email protected]> wrote: >> On Fri, Jan 23, 2009 at 08:17, [email protected] < >> >> [email protected]> wrote: >> >>> Standard servlets create a new thread per request but from a few >>> simple test i have run this appears not to be the case with GWT. >> *Wrong*. >> >> Standard servlets create *one* instance per application container. Multiple >> threads can be calling the servlet at once. >> >>> Why is this and is there any way to do this other than explicitly >>> creating a new thread at each method my service exposes. >> Because GWT is following the standard servlet conventions... it is after all >> running a standard servlet container (Tomcat) in its hosted mode debugging >> tool. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
