On Friday Jun 9, 2000, Stefaan A Eeckels wrote:
>
> On 09-Jun-2000 Michael Thome wrote:
> > I think the best answer is to do the second tier threading in userspace
> > (best would be in glibc). The kernel folks have some good points
> > about doing it the kernel but seem to have a mental block as to why
> > you'd *ever* want hundreds of threads in a single app.
> I'm not one of the kernel folk, but can you give me an example of
> an application that would be impossible without hundreds of threads?
> Or even one that would significantly benefit from hundreds of threads?
A performance critical application server that needs to handle
hundreds of simultaneous requests and wants to keep a pool of
threads around so as to not re-instantiate a client thread per
incoming request.
Just a hypothetical example. :-)
-John
----------------------------------------------------------------
John Rousseau [EMAIL PROTECTED]
SilverStream Software Phone: +1 978 262 3564
2 Federal Street Fax: +1 978 262 3499
Billerica, MA 01821 http://www.silverstream.com
----------------------------------------------------------------
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
