On the server side there is generally a pool of threads held by the server. Thus a single "session" (in the JSESSIONID sense of Session) may involve any number of threads from the pool. Each request is processed on a single thread taken from the pool.
So to answer your question: chances are it won't start a new thread, but the 2 can execute at the same time. Just bare in mind that the /browser/ generally limits you to 2 concurrent connections per server. Hope that explains things a bit ;) // J ralph wrote: > > I understand that the client side is asynchroneous, which means that I > can call a new function from the client side to the server side > without waiting for the previous function to be completed. Now how > does this work on the server side? I thought that there was only a > single thread per session on the server side. But let's say I call a > function getEvent() and hang it on the server to produce the comet > effect (long polling) and try to call another function meanwhile, what > would happen on the server side? Would the next call hang till the > first one finishes? would it open a new thread? > > Thanks. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
