--
Gunther,
Pierpaolo Fumagalli has understood and answered the question right.
Thread pooling is a common mechanism that takes the advantage of threads
(as you have correctly pointed out) to the next level. Instead of creating
a fresh new thread for every request, the server keeps a pool of thread.
When a request comes in, it routes the request to one of the threads.
Several algorithms are available to pick the thread (round robin, random,
or history based) for best load balancing.
As a servlet developer you should see no change in things except for may be
better performance.
Apacahe already uses thread pools in NT. According to Pierpaolo JServ will
support it in 1.0.1.
Bibhas.
----------
> From: Guenther Wieser <[EMAIL PROTECTED]>
> To: Java Apache Users <[EMAIL PROTECTED]>
> Subject: Re: Thread question
> Date: July 2, 1999 6:10 AM
>
> --
>
> Sorry, I can't tell you about using a thread pool (or only the few
> things following in the next section), but I think creating a new thread
> for each request is one of the best features of servlets.
> It makes sure that your servlet can respond in every situation, and it's
> much less memory and cpu usage than with C, C++ or perl which spawn a
> new process for every request (plus all the init overhead).
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
