Nathan Meyers wrote,
> But I'm always curious about "wacky people" who like
> to use thousands of threads (or tons of memory or
> zillions of levels of recursion, etc.). Is that
> approach fundamental to solving the problem
> efficiently, or do you use it because it's convenient
> and/or cool?
Err ... is that a serious question?
Suppose I'm writing an HTTP server, and my architecture
comes out cleanest if I can assign one thread per
request, and I want to be able to support more than
256 concurrent requests. For "HTTP server" feel free
to substitute anything comparable.
Within the terms in which you phrased the question I
guess the answer has to be "because it's convenient",
but I think it goes a bit deeper than that.
Cheers,
Miles
--
Miles Sabin Cromwell Media
Internet Systems Architect 5/6 Glenthorne Mews
+44 (0)181 410 2230 London, W6 0LJ
[EMAIL PROTECTED] England
