Michael Thome <[EMAIL PROTECTED]> writes: > > Agreed - beginners *do* tend to use too many threads, This has nothing to do with "beginners"! Currently, you *cannot* write a Web server in Java without using one thread per socket connection. You can limit the number of "active" connections, and queue up new incoming connections until a thread in your "pool" becomes available, but eventually this does not scale, and your users get angry at the long wait times. The solution is to either (a) fix threads or (b) introduce nonblocking I/O into Java. We (the expert group for JSR 51) is currently doing (b). I am proposing that (a) is useful as well. Matt Welsh ---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
- Re: JavaOne - no green threads for Linux Nelson Minar
- Re: JavaOne - no green threads for Linux Matt Welsh
- Re: JavaOne - no green threads for Linux Juergen Kreileder
- Re: JavaOne - no green threads for Linux Diego Pons
- Re: JavaOne - no green threads for Linux Michael Thome
- Re: JavaOne - no green threads for Linux Matt Welsh
- Re: JavaOne - no green threads for Linux Michael Thome
- Re: JavaOne - no green threads for Linux Dimitris Vyzovitis
- Re: JavaOne - no green threads for Linux Michael Thome
- Re: JavaOne - no green threads for Linux Matt Welsh
- Re: JavaOne - no green threads for Linux Matt Welsh
- Re: JavaOne - no green threads for Linux Michael Thome
- Re: JavaOne - no green threads for Linux Nathan Meyers
- Re: JavaOne - no green threads for Linux Nelson Minar
- Re: JavaOne - no green threads for Linux Nathan Meyers
- Re: JavaOne - no green threads for Linux Nathan Meyers