MPM - connection

[Andrew Hole <andremailinglist@xxxxxxxxx>]

Hi!

 

I was reading an interesting document http://httpd.apache.org/docs/2.0/misc/perf-tuning.html about MPM and I would like to clarify a doubt regarding the concept of connection:

    *  The worker MPM uses multiple child processes with many threads each. Each thread handles one connection at a time. Worker generally is a good choice for high-traffic servers because it ha

s a smaller memory footprint than the prefork MPM.
    * The prefork MPM uses multiple child processes with one thread each. Each process handles one connection at a time. On many systems, prefork is comparable in speed to worker, but it uses more memory. Prefork's threadless design has advantages over worker in some situations: it can be used with non-thread-safe third-party modules, and it is easier to debug on platforms with poor thread debugging support.

What means "Each process/thread handles one connection at a time?" A connection is a request made by the client? A thread just handle a request?

Thanks

Best Regards