Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 41531 invoked by uid 500); 19 Dec 2000 04:03:22 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 41520 invoked from network); 19 Dec 2000 04:03:20 -0000 Date: Mon, 18 Dec 2000 20:05:59 -0800 (PST) From: rbb@covalent.net X-Sender: rbb@localhost To: new-httpd@apache.org Subject: Re: AddModule (was: Re: cvs commit: httpd-2.0 STATUS) In-Reply-To: <20001218200152.R30887@lyra.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > > This is actually not true. There is still a minor use for the AddModule > > directive. If there are multiple modules, which do not have a hard and > > set order dependance, then AddModule can and should be used to order the > > modules correctly. I had originally thought this could be removed as > > well, but I no longer believe this is true. > > We add them all at startup time. That certainly doesn't obey any particular > ordering whatsoever. :-) That's what ClearModuleList is for. :-) > > Can you specify a case where the ordering must be controlled with the use of > AddModule? I thought we were past that now. mod_auth_db and mod_auth. mod_rewrite and mod_proxy. I could come up with more if pressed. Ryan _______________________________________________________________________________ Ryan Bloom rbb@apache.org 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------