httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From elu...@apache.org
Subject svn commit: r1729945 - /httpd/httpd/trunk/docs/manual/mod/event.xml
Date Fri, 12 Feb 2016 07:29:19 GMT
Author: elukey
Date: Fri Feb 12 07:29:19 2016
New Revision: 1729945

URL: http://svn.apache.org/viewvc?rev=1729945&view=rev
Log:
Removed confusing parts in the Limitations section of the mod_event's doc page.


Modified:
    httpd/httpd/trunk/docs/manual/mod/event.xml

Modified: httpd/httpd/trunk/docs/manual/mod/event.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/event.xml?rev=1729945&r1=1729944&r2=1729945&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/event.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/event.xml Fri Feb 12 07:29:19 2016
@@ -104,16 +104,12 @@ of the <directive>AsyncRequestWorkerFact
         All modules shipped with the server are compatible with the event MPM.</p>
 
         <p>A similar restriction is currently present for requests involving an
-        output filter that needs to read and/or modify the whole response body,
-        like for example mod_ssl, mod_deflate, or mod_include. If the
-        connection to the client blocks while the filter is processing the
+        output filter that needs to read and/or modify the whole response body. 
+        If the connection to the client blocks while the filter is processing the
         data, and the amount of data produced by the filter is too big to be
         buffered in memory, the thread used for the request is not freed while
-        httpd waits until the pending data is sent to the client. Please note that
-        this limitation is only a corner case, it does not mean that the event MPM
-        defaults to worker in presence of TLS/SSL connections and/or compression.</p>

-        
-        <p>To illustrate this point we can think about the following two situations:

+        httpd waits until the pending data is sent to the client.<br /> 
+        To illustrate this point we can think about the following two situations: 
         serving a static asset (like a CSS file) versus serving content retrieved from
         FCGI/CGI or a proxied server. The former is predictable, namely the event MPM 
         has full visibility on the end of the content and it can use events: the worker 



Mime
View raw message