Hey kids, As well as spending far too much time in #apache I occasionally chip in on the #rubyonrails irc channel. Quite frequently when people ask questions about apache there the response is to use this or that other web server/load balancer instead. Lighttpd, nginx & pound seem to be popular alternative recommendations.
I've asked a few times why people say these things and the responses tend to include: * Apache's too complex to configure * Apache's bloated * Apache does too much stuff I don't need * Apache's slow Generally people make pains to say that the slowness thing is perceived and not important, perhaps realising that they're talking in a rails channel :-) So I'm wondering what can be done about any of this. Perhaps: * Remove obsolete modules from the default build * Reduce the size of the default config files * Document minimal/specialist configurations * Make mod_proxy_balancer less confusing The third option is the only one here I feel I can help with. Can I have a show of hands on the idea of creating a section of the docs to demonstrate minimal and specialist configurations? After all, there's only *one* mandatory directive (Listen). [ ] Yes please [ ] No, because: [ ] Meh -- noodl --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
