Akins, Brian wrote:
On 4/3/08 11:38 AM, "William A. Rowe, Jr." <[EMAIL PROTECTED]> wrote:
But that *doesn't* mean I don't want it... simply not to replace directory,
file, location or method. Keep in mind you wouldn't have your ErrorLog
opened at startup time, as this is too variant
Unless I'm mistaken, there is nothing that really stops us from making all
log related directives from being per-dir (assuming they have "real" names
at startup).
Using mod_log_config as an example, it opens all of it's logs as root at
start, and we are able to select one at run time via env. That could just
as easily be done via a per-dir merge.
(Note: I am ignorant of the stuff between the errolog directive until it
gets to the actually logging stuff, so I may be way off. )
You are right; provided that we pre-merge SOME of the layers of dir configs
(e.g. we pre-merge all of the vhost-related dir configs).
And remember a merge of A+null or null+A is fast. So if we break up a very
very big dir config structure into three, e.g. those directives that are
very frequently tweaked, those which are sometimes tweaked and those we
don't expect to change at all (at least, not after server-merges at startup)
the overall hit of dir_merge (now three different functions for this
hypothetical modules) will be much less.
