httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <>
Subject Re: cvs commit: httpd-2.0/server config.c
Date Mon, 22 Jan 2001 02:06:09 GMT
I suspect this is a no-win situation.  I'd suggest we can lose them, if we
set up the architecure correctly.  To load three modules from the same .dll
is very simple, use loadmodule three times with three different module names.
But we would need to drop the 'bundled' set in favor of the loaded modules
list consisting of just core, and a list of AddModules in httpd.conf (some
enabled, some disabled, all changable.)  The one asset to AddModule, however,
is that it's easily passed with the -c "AddModule foo_module" syntax.


----- Original Message ----- 
From: <>
To: <>
Sent: Sunday, January 21, 2001 3:02 PM
Subject: Re: cvs commit: httpd-2.0/server config.c

> > > If we could... that would be great. And re: your STATUS change: yes, I'd
> > > think that both AddModule and ClearModuleList would go away. With the hook
> > > and handler ordering, I wouldn't think there is any more reason to need to
> > > use AddModule to "establish an ordering [of modules]".
> > 
> > Making the API change now.  I think you are correct about AddModule, so it
> > will go away later today.
> Ohh,  just thought of something else though.  Let's assume we are on
> Windows, where we distribute a binary with a lot of modules
> installed.  With out ClearModuleList and LoadModule, all of those modules
> are always active.
> Will, any feelings about this?
> Ryan
> _______________________________________________________________________________
> Ryan Bloom              
> 406 29th St.
> San Francisco, CA 94131
> -------------------------------------------------------------------------------

View raw message