httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Laurie <...@algroup.co.uk>
Subject Re: AddOutputFilter enhancement
Date Sat, 03 Feb 2001 13:05:50 GMT
rbb@covalent.net wrote:
> 
> > > > > 1)  SetupFilterStack   Stack_name   filter1 filter2 etc
> > > > > 2)  AddFilterStack     Stack_name   extension1 extension2 etc
> > > > > 3)  SetFilterStack     Stack_name   mime-type1 mime-type2 etc
> > > >
> > > > This doesn't mean anything to me - would you like to add some
> > > > explanation to your explanation?
> > >
> > > The idea is to clean up the interface a bit.  Basically, directive #1
> > > would define a filter stack, which could then be used in the other
> > > two.  The other two directives are basically just like AddType and
> > > SetType, except instead of associating a mime-type with an extension or a
> > > handler, it associates a defined filter stack with either a mime-type or
> > > an extension.
> >
> > Oh, I see ... why is this better than <Files...>?
> 
> Because I got yelled at when I said to use <Files...>.  :-)  I was just
> trying to make people happy.

No-one's yelling about using <Files...> now - in fact, I see only
agreement.

> > I have to say I don't like the idea of associating with mime-types,
> > since those are related to the end product, and hence are likely not to
> > be unique to a particular filter stack - or did you mean to match
> > handlers, really?
> 
> I guess handlers.

Which makes AddFilterStack redundant already (do AddHandler and
SetFilterStack instead). Not that I'm advocating this approach at all
:-)

Cheers,

Ben.

--
http://www.apache-ssl.org/ben.html

"There is no limit to what a man can do or how far he can go if he
doesn't mind who gets the credit." - Robert Woodruff

Mime
View raw message