Maybe I'm answering the wrong question here, but aren't request
handling threads re-used by default in most servlet containers? On something
like Tomcat you've got a fixed pool of worker threads, and every request has
to be served by one of this (relatively static) members of the thread pool.
So by the time you've handled a few thousand requests, each thread has been
re-used dozens and possibly hundreds of times.
Or are you talking about a different kind of thread here?
--- Pat
> -----Original Message-----
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Kent Tong
> Sent: Wednesday, August 31, 2005 8:45 AM
> To: [email protected]
> Subject: Could a request handling thread be reused?
>
> Hi,
>
> A colleague brought up an interesting issue: Could a request handling
> thread be reused for different requests? I've checked the servlet
> specification and can't find anything prohibiting this. So, in
> principle, this should be possible. In that case, the extensive use
> of thread-modeled hivemind services in Tapestry 4 may break in some
> containers?
>
> --
> Author of an e-Book for learning Tapestry
> (http://www.agileskills2.org/EWDT)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
