On Friday 15 May 2009 16:07:11 Christopher Schultz wrote: > Rainer, > > On 5/15/2009 2:37 AM, Rainer Frey (Inxmail GmbH) wrote: > > is the assumption that one request is processed by one thread (and never > > passed to another during processing) true for all connectors, including > > NIO? > > Are you asking if the request is passed to another thread at any point > for processing?
Exactly, in my case I'm interested in the span between entering the application's filter chain and returning from it in the outmost filter. > Not likely, since Java doesn't support continuations. > The request handler thread should handle the request from start to finish. Is this explicitly stated somewhere? There could theoretically be a queue of Request/Response pairs, and different threads could pick one up, execute one element in the filter chain, and put the pair back for the next thread. > The servlet spec goes on to require (in section 8.2) that the container > dispatches sub-requests (includes or forwards) using the same thread > that was originally chosen to handle the primary request. I just read this up. It says "should ensure". How strong this is sepends on whether this has RFC "SHOULD" characteristics, or is merely a recommendation. > I think you're safe. I guess so too, but it's nice to hear opinions of people with insightinto internals. > -chris Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
