From 7e88ceb1f6ac60f64232a1a10d796ac82849ddb8 Mon Sep 17 00:00:00 2001 From: Daniel Gruno Date: Fri, 20 Apr 2012 10:19:59 +0000 Subject: [PATCH] Fixing some typos git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1328296 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/event.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/manual/mod/event.xml b/docs/manual/mod/event.xml index 59c6e15cb9..81275a3a75 100644 --- a/docs/manual/mod/event.xml +++ b/docs/manual/mod/event.xml @@ -50,7 +50,7 @@ of consuming threads only for connections with active processing

This MPM tries to fix the 'keep alive problem' in HTTP. After a client completes the first request, the client can keep the connection open, and send further requests using the same socket. This can - save signifigant overhead in creating TCP connections. However, + save 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 thread to handle both @@ -155,7 +155,7 @@ of consuming threads only for connections with active processing needed, and other (mostly SSL) connections with one request worker thread reserved per connection. This can lead to situations where all workers are tied up and no worker thread is available to handle new work on established - async connetions.

+ async connections.

To mitigate this problem, the event MPM does two things: Firstly, it limits the number of connections accepted per process, depending on the -- 2.40.0