httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Laurie <...@algroup.co.uk>
Subject Re: Order of handlers
Date Sun, 31 Dec 2000 16:53:38 GMT
"William A. Rowe, Jr." wrote:
> 
> > From: Ben Laurie [mailto:ben@algroup.co.uk]
> > Sent: Sunday, December 31, 2000 8:10 AM
> >
> > > > From: Ben Laurie [mailto:ben@algroup.co.uk]
> > > > Sent: Sunday, December 31, 2000 7:04 AM
> > > >
> > > > Anyway, I propose that, like hooks, handlers should be able to specify
> > > > their relative order, when they feel like it. And I think I'm
> > > > volunteering to make the change :-)
> > >
> > > Do you plan to provide an 'override' such that module authors, especially,
> > > can force a reorg?
> 
> Let us suppose we have modules that are round-robin, such as authorization.
> Wouldn't it make sense to allow the administrator to 'push' an authorization
> module before or after another such module?

Yes.

> 
> > I don't understand what you mean by this.
> 
> Expecially for module authors who are trying to determine the side-effects
> of their module's placement.  Sure beats recompiling dozens of times.

Gotcha.

> > >  Heck, maybe an .html on "Why does Apache order modules
> > > thusly, and where should I stick my module?"
> >
> > I'm trying to eliminate the need to answer that question...
> 
> Understood ... module authors still need to understand the concept.
> 
> What about a delta argument after the addmodule/loadmodule modname argument?
> So if it's +3, I'm moving it's order by 3 (forward?  backwards?  good q.)
> If a module publisher is trying to accomplish something specific, they can
> document what to set that arg, and why, and what the side effects are.

Ick. No. That's why we have tsort for hooks. Anyway, I'm about to write
a more detailed missive.

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