Exactly. The idea is to keep I/O events isolated to the main driver
thread, which in theory should be more efficient. The goal is to not tie
up connection threads, and have them sitting idle waiting for I/O.
This model is kind of the best of both worlds - single-threaded event
loop that accepts connections and consumes the request, and
multi-threaded connection threads to do the actual work of the request.
The ideas are similar to work that's discussed here:
http://www.eecs.harvard.edu/~mdw/proj/seda/
At least this is how I remember things... ;-)
- Nathan
Tom Jackson wrote on 5/11/2004, 3:23 PM:
> You have to read all the data anyway, but
> now the POSTed data is read in so you don't have a tcl procedure slowly
> reading data and controlling the connection.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
