Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Errors-To: <wrowe@rowe-clan.net>
From: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
To: <new-httpd@apache.org>
Subject: RE: Order of handlers
Date: Sun, 31 Dec 2000 09:01:24 -0600
Message-ID: <000a01c0733a$8bf2daa0$92c0b0d0@roweclan.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <3A4F3E29.F2AFAF37@algroup.co.uk>
Importance: Normal

> 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?

> 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.

> >  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.