Dan Poirier wrote:
William A. Rowe, Jr. wrote:
[EMAIL PROTECTED] wrote:
@@ -443,8 +443,8 @@
<directivesynopsis>
<name>MaxClients</name>
-<description>Maximum number of child processes that will be created
-to serve requests</description>
+<description>Maximum number of simultaneous requests that will
+be served</description>
perhaps we mean to say
"Maximum number of connections that will be processed simultaneously"
which is, as you note, different than the number served, lingering,
sitting in the accept queue, etc.
also note that clients in this day and age typically consume 2
connections so that description was sub-par.
Maybe all we can say these days about MaxClients is "Maximum number of
worker threads that will be created," since the event MPM could have
more connections or requests in progress than threads.
The problem is that we don't want to confuse threads/processes with max
clients. And event matches my description. more requests may be pending,
but not be processed simultaneously.
