On 2004.08.17, Stephen Deasey <[EMAIL PROTECTED]> wrote: > This isn't true. In AOLserver, once a request has completed the conn is > returned to the driver thread for keepalive. It's monitored in a > non-blocking fashion until either it times out or the client makes > another request. In the meantime, the conn thread which just completed > is free to service other requests.
Um, what about protocols that requires the server to maintain state with the connection? If the thread servicing the connection gets returned to the pool, doesn't the state go along with it? > This makes it possible to have 1000 concurrent connections serviced by a > pool of just 10 threads -- at any one time most of the connections will > be momentarily idle. This benefits memory usage and context switch > overhead. This is only desirable for stateless protocols, like HTTP. > This is one of the major architectural benefits AOLserver has over > something like Apache. In the Apache model, processes take turns > listening for connections. When a connection arrives, the process > switches roles from a listener to a worker and processes the > connection. The worker processes the connection to completion, > including idle wait time due to keepalive. True, for stateless protocols like HTTP, the AOLserver model is superior. For stateful protocols, this may not work so well. > AOLserver is ideally suited to the majority of server tasks. About the > only shortcoming which comes to mind is that conn threads are required > to do blocking writes. But fixing that would be of benefit to the HTTP > processing side too. So, we want reader threads and separate writer threads now, too? Exactly how many free-range threads do we want roaming the server prairie, here? > > Of course, we're both only speculating here. > > Speak for yourself! Show me your measurements. And I'm not talking 36D-28-34, either. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- 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.
