svn commit: r1823833 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.html.en

[el...@apache.org]

Author: elukey
Date: Sun Feb 11 11:09:35 2018
New Revision: 1823833

URL: http://svn.apache.org/viewvc?rev=1823833&view=rev
Log:
documentation rebuild

Modified:
    httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.html.en

Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.html.en?rev=1823833&r1=1823832&r2=1823833&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.html.en Sun Feb 11 11:09:35 2018
@@ -99,8 +99,9 @@
     By default mod_proxy (configured with <code>enablereuse=on</code>)
     allows a connection pool of
     <code class="directive"><a href="../mod/mpm_common.html#threadsperchild">ThreadsPerChild</a></code> connections to the
-    backend for each httpd process, so the following use cases should be taken
-    into account:</p>
+    backend for each httpd process when using a threaded mpm (like
+    <code class="module"><a href="../mod/worker.html">worker</a></code> or <code class="module"><a href="../mod/event.html">event</a></code>),
+    so the following use cases should be taken into account:</p>
     <ul>
       <li>Under HTTP/1.1 load it will likely cause the creation of up to
       <code class="directive"><a href="../mod/mpm_common.html#maxrequestworkers">MaxRequestWorkers</a></code>