From: "Nic Ferrier" <[EMAIL PROTECTED]>
> But that's not how containers work, the container will grow the
> thread pool to the size needed. As new requests come in there will be
> new threads.
Why do this? Why create more threads? Creating threads takes time, and there
is a period
when the threads wake up where you have a thread-rush, a hugh number of
threads that are now active.
>
> And as long as these blocked threads are really blocked then a decent
> threading implementation (eg: green threads) won't actually create any
> more processing overhead because the thread layer should be
> implemented as a swappable pool of OS threads.
>
"then a decent threading implementation"
perhaps, but what implementations are decent?
I'm a strong believer that you can't abstract-out the concept of threads
from a well written server. My solution is simple to implement, and puts
control in the server developers hands where it belongs.
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
