>
> well if they are aliased then they are literally the same
> function, right? so we're still not talking separate
> configs, since they point to the same data...
>
> I'm not through with my second bowl of coffee yet, though :)
ok, scratch that - I see the code now...
so, now I'm wondering if we need the distinction between the per-server and
per-dir configs for the reasons I mentioned before.
it seems there are few directives in mod_perl that really should be limited
to a per-server scope - PerlTaint and PerlWarn, PerlFreshRestart, etc...
actually in 2.0 this will be kinda cool, since I'm guessing each vhost can
have its own interpreter pool so you really can have PerlTaint on a vhost
basis, unlike 1.x...
all the others should be merge-able on a per-dir basis. which means they can
be held in the per-dir config only, provided Apache 2.0 follows the same
null config that 1.3 does for per-dir directives outside of a container.
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
