From: Jeff Trawick <trawick@apache.org>
Date: Mon, 20 Aug 2012 13:13:30 +0000 (+0000)
Subject: describe some interesting differences from Unix MPMs
X-Git-Tag: 2.5.0-alpha~6401
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=325ed03badf45e3f931f2cc265cd765839033646;p=apache

describe some interesting differences from Unix MPMs


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1375006 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/mod/mpm_winnt.xml b/docs/manual/mod/mpm_winnt.xml
index 7960d1cbc8..5d8c2d265b 100644
--- a/docs/manual/mod/mpm_winnt.xml
+++ b/docs/manual/mod/mpm_winnt.xml
@@ -55,6 +55,40 @@ NT.</description>
     <code>none</code>.  <em>In Apache httpd 2.0 and 2.2,
     <directive>Win32DisableAcceptEx</directive> was used for this purpose.</em></p>
 
+    <p>The WinNT MPM differs from the Unix MPMs such as worker and event
+    in several areas:</p>
+
+    <ul>
+      <li>When a child process is exiting due to shutdown, restart, or
+      <directive module="mpm_common">MaxConnectionsPerChild</directive>,
+      active requests in the exiting process have
+      <directive module="core">TimeOut</directive> seconds to finish before
+      processing is aborted.  Alternate types of restart and shutdown are not
+      implemented.</li>
+
+      <li>New child processes read the configuration files instead of
+      inheriting the configuration from the parent.  The behavior will
+      be the same as on Unix if the child process is created at startup
+      or restart, but if a child process is created because the prior
+      one crashed or reached 
+      <directive module="mpm_common">MaxConnectionsPerChild</directive>,
+      any pending changes to the configuration will become active in the
+      child at that point, and the parent and child will be using a
+      different configuration.  If planned configuration changes have been
+      partially implemented and the current configuration cannot be
+      parsed, the replacement child process cannot start up and the server 
+      will halt.  Because of this behavior, configuration files should not
+      be changed until the time of a server restart.</li>
+
+      <li>The <code>monitor</code> and <code>fatal_exception</code> hooks
+      are not currently implemented.</li>
+
+      <li><directive>AcceptFilter</directive> is implemented in the MPM
+      and has a different type of control over handling of new connections.
+      (Refer to the <directive module="core">AcceptFilter</directive>
+      documentation for details.)</li>
+    </ul>
+
 </summary>
 
 <seealso><a href="../platform/windows.html">Using Apache HTTP Server on Microsoft Windows</a></seealso>