From eb7dac421a99cff3370fb62073f89e99c35a45e7 Mon Sep 17 00:00:00 2001 From: Luca Toscano Date: Mon, 2 May 2016 19:31:21 +0000 Subject: [PATCH] Fixed wording about the event's doc page after Mike's feedback on dev@ git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1742031 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/event.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/manual/mod/event.xml b/docs/manual/mod/event.xml index a5fa344ece..5a9162333a 100644 --- a/docs/manual/mod/event.xml +++ b/docs/manual/mod/event.xml @@ -61,15 +61,15 @@ of the AsyncRequestWorkerFactor.

significant overhead in creating TCP connections. However, Apache HTTP Server traditionally keeps an entire child process/thread waiting for data from the client, which brings its own disadvantages. - To solve this problem, this MPM uses a dedicated listener thread for each process - to handle both the Listening sockets, all sockets that are in a Keep Alive state, + To solve this problem, this MPM uses a dedicated listener thread for each process + to handle both the Listening sockets, all sockets that are in a Keep Alive state, sockets where the handler and protocol filters have done their work and the ones where the only remaining thing to do is send the data to the client.

-

This new architecture, leveraging non blocking sockets and modern kernel +

This new architecture, leveraging non-blocking sockets and modern kernel features exposed by APR (like Linux's epoll), - does not require anymore the mpm_accept Mutex + no longer requires the mpm-accept Mutex configured to avoid the thundering herd problem.

The total amount of connections that a single process/threads block can handle is regulated -- 2.40.0