From: Luca Toscano <elukey@apache.org>
Date: Mon, 4 Sep 2017 15:46:21 +0000 (+0000)
Subject: event.xml doc: update to latest improvements
X-Git-Tag: 2.5.0-alpha~167
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=48891d3234aff3d55bfcd9c06504e89f58542890;p=apache

event.xml doc: update to latest improvements

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

diff --git a/docs/manual/mod/event.xml b/docs/manual/mod/event.xml
index c92a394dfd..f1a4fcf93d 100644
--- a/docs/manual/mod/event.xml
+++ b/docs/manual/mod/event.xml
@@ -102,6 +102,13 @@ of the <directive>AsyncRequestWorkerFactor</directive>.</p>
 
         <p>These improvements are valid for both HTTP/HTTPS connections.</p>
 
+        <p>The above connection states are managed by the listener thread via dedicated queues, that up to 2.4.27 were checked every 100ms
+        to find which connections hit timeout settings like <directive module="mpm_common">Timeout</directive> and
+        <directive module="core">KeepAliveTimeout</directive>. This was a simple and efficient solution, but it presented a downside: the pollset was
+        forcing a wake-up of the listener thread even if there was no need (for example because completely idle), wasting resources. From 2.4.27
+        these queues are completely managed via an event based logic, not relying anymore on active polling.
+        Resource constrained environments, like embedded servers, may benefit from this improvement.</p>
+
     </section>
 
     <section id="graceful-close"><title>Graceful process termination and Scoreboard usage</title>