Is it really needed?
You make an excellent arguement for it, but I have seen sites with literally thousands of connections running on minimal hardware that didn't get brought down as you suggest would happen.
I've seen them get slowed down by heavy traffic, but not crashed.
It is actually far more efective to kill keepalive completely, since it then shuts the process down as soon as the file is sent.
or, let apache use it's builtin threading capacity, so each child process can have threaded processes in it without having to spawn new instances of apache to handle them. Even though Apache 2 has threading capability, it is not usually enabled by default. to enable this you would have to build Apache from sources.
An important thing to remember if you do chose to build from sources is that you have to pick what modules will be built into the server and which will be addon modules. Apache has a core of 40 modules that are available to be built in.
[ little things like the http protocol is a module ]
If you are building from sources, you might want to look at both mod_fortress and mod_dos_evasive for the security of the server, mod_fortress is a firewall in apache for apache. mod_dos_evasive is a module designed to fight ddos attacks.
[ 240+ modules for Apache2 and another 240+ modules for Apache 1, any of which can be built into apache as well as being an addon module. I'm currently working on getting mod_asp and mono to function in apache, so I can detail how to add asp and .net to apache. ]









































