httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Prud'hommeaux" <e...@w3.org>
Subject Re: cvs commit: apache-1.3/src CHANGES
Date Sat, 14 Nov 1998 00:57:40 GMT
On Tue, 10 Nov 1998, Tony Finch wrote:

> Jim Jagielski <jim@jaguNET.com> wrote:
> >Ben Hyde wrote:
> >> 
> >> The new configure mechanism is just plain better we should cling
> >> to that one fact.
> >
> >Well, some would argue whether it is or not. Some people prefer
> >editing Configuration and then typing Configure over using configure.
> 
> Although I'm generally a fan of no-brain automatic configure scripts,
> I'm a bit leery of APACI mainly because of the extent to which Apache
> is configured at compile time (and given that we have many thousands
> of web sites running on Apache we have to do this reasonably
> carefully). The Configuration file has the advantage that you can add
> a commentary on the decisions you made when editing it.



> A second-best option would be to use mod_so and leave module
> configuration to the httpd.conf file rather than to obscure
> compile-time options that can be easily lost, but this has
> implications for portability and performance.
> 
> I certainly dislike the idea of complicated command-line options to
> APACI configure that permute the order of the modules.

I don't use DSO but still put this in my httpd.conf to handle the
ordering:
ClearModuleList
AddModule mod_env.c
AddModule mod_log_config.c
AddModule mod_mime.c
...
Possibly I have inadvertantly enabled DSO, but I don't believe so.
Just make sure you don't put AddModule http_core.c at the top.

-eric


Mime
View raw message