On Thursday 16 June 2011, William A. Rowe Jr. wrote: > On 6/16/2011 4:18 AM, bswen wrote: > > I think the only major problem of httpd is its "one thread per > > connection" I/O model. It's an inherently unscalable design. > > Httpd-3.0 will be meaningless if it keeps on this i/o design. > > That is no longer its design; it is now "one thread per request". > > Intra-connection mechanics are now handled in an event loop when > using the event mpm, and this is worked well in real life. Some > modules which manipulate the connection or make connection-scope > assumptions about threading will be require the user to stay on > worker or prefork, of course. > > Long lived requests still pose a challenge.
I think the more urgent challenge lies with ssl, for which we still have the one-thread-per-connection principle.
