> Apache will switch to this method at some point. I really can't
> understand why they went with that complicated pre-forking stuff.
> Using non-blockijng I/O is just not that hard."
As mentioned previously, due to the blocking semantics of file I/O on unix,
single process servers will only provide peak throughput if everything is
resident. By pre-forking, data can continued to be served if one process blocks
on file I/O. Apache already handles multiple connections within a process, so
it does something like this already.
-Kip
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
