On Sun, 2 Sep 2001, Justin Erenkrantz wrote:
> Yuck, yuck, yuck, yuck, yuck. (Did I mention I think this is yucky?)
Let me propose something way out in left field. Feel free to shoot it
down.
Problem: filters configuration is damn confusing. I only have time to
skim new-httpd (err, dev@httpd), but I've completely lost track of how to
configure filters. How do they inherit from one context to another? How
are they ordered? Where can they be used? What is the syntax? I can
only imagine how confused the users are going to be.
Solution: make filters a back-end concept that is not directly accessible
to users. Remove all user-level filter controls. Any module that
provides a filter must also provide configuration directives to activate
it (ie, IncludesFilter On).
Perhaps this is just a straw-man, but unless someone is planning to write
one helluva good set of docs for this stuff, I pity the people trying to
use it.
[By the way, I retract any objections to OtherBills proposed changes. I
don't understand this stuff well enough to have an informed opinion.]
Joshua.
