[EMAIL PROTECTED] wrote:
The SEDA article discusses an approach where you mix a single-threaded event driven piece, in our case it could be the driver thread, with multi-threaded workers, the connection threads. The idea is to avoid having the connection threads, which are relatively precious resources, from sitting around idle waiting on things like I/O.
...
The main point of this approach is to move the I/O events up into the single-threaded driver thread, and to avoid waiting on events in your connection threads. That's roughly the idea at least. ;-)
Hopefully that makes sense?
Yes, it makes sense, though I'm not sure how much sense it makes in the context of the typical kind of website we build with AOLserver.
This brings up an interesting point. What kinds of Web sites and applications do folks typically build with AOLserver? At AOL we were discussing using such a feature for sites which include many Web service calls to other systems, and for other things like server-side ad system calls, etc.
-- 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.
-- 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.
