From 7dd32bed0ad25c9aa4919fdb8818480c23e53d1f Mon Sep 17 00:00:00 2001
From: Daniel Gruno 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
@@ -150,7 +150,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.
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