There is also a follow up article written by one of the httpd developers about 'What Apache brings to the table.' The article cites community, experience, legal framework, diversity, brand strength, and networking as reasons why developers and companies should consider bringing their projects over to Apache."
Two words why you shouldn't use Apache unless you absolutely need to (and most apache users don't NEED apache): configuration complexity.
Apache's configuration file hasn't changed dramatically since
Yes, Apache (Web server) is somewhat hard to configure. There's a large file with a lot of (documented) features and settings, and a lot of ways to go wrong there. On the other hand, Apache is incredibly flexible: You can use it as a proxy, it does ssl, it fronts for Java Web servers, it rewrites URLs, it authenticates, it slices, it dices and I'm probably just scratching the surface.
Someone who knows his way around the config file - and that's really the only crucial thing to know about Apache - is able to
I really wish that there were a programmatic interface to Apache configuration.
I think we could really use some tools to help with Apache configuration.
Something where, in any directory, you could ask: "Apache, tell me what you think about this directory. Talk to me, Mother Goose." You know- it could say, "Options ExecCGI, blah, blah, and blah." It would tell you if Apache had permission to go to that directory, it could tell you what rights Apache had in that directory, it could tell you what things it would do in that directory. That tool, right there, would end SO MANY HEADACHES.
Something to programmatically change the Apache configuration. Why is this important? INSTALLERS. You can make automatic installers that don't mess up your other Apache stuff, if you could do this. That will result in speeding up web service deployments, and head us toward web component utopia.
configuring apache #1 complaint, still unaddressed (Score:2, Interesting)
Two words why you shouldn't use Apache unless you absolutely need to (and most apache users don't NEED apache): configuration complexity.
Apache's configuration file hasn't changed dramatically since
Configuration complexity (Score:5, Insightful)
On the other hand, Apache is incredibly flexible: You can use it as a proxy, it does ssl, it fronts for Java Web servers, it rewrites URLs, it authenticates, it slices, it dices and I'm probably just scratching the surface.
Someone who knows his way around the config file - and that's really the only crucial thing to know about Apache - is able to
Re:Configuration complexity (Score:2)
I think we could really use some tools to help with Apache configuration.