"David N. Welton" wrote:
> [...]
>
> Create new top-level commands for the .htaccess configurable commands.
> Has the advantage of going along with Apache's normal way of doing
> things - the disadvantage is of course backwards compatibility.
Backward compatibility is not so much an issue, as long as you don't need
to change code in scripts. When I install a new version of a package, I
can always expect some change in configuration methods.
> Create and muck around with a merge_config functions. The advantage
> here is that we can fine-tune the commands to accept what we want,
> with the downside being that it may be confusing to someone who is not
> familiar with the C code what is going on.
Too complex, IMHO.
> Tweak things at the level of 'set_script'. Advantage: we get
> fine-grain control. Disadvantage: once again, we are
> replicating/mucking with something that Apache ought to be controlling
> on its own.
I agree.
> Any thoughts on which one people might prefer? None of them really
> jumps out at me as the optimal way of doing things, although the
> merge* may be the best of the bunch, at a glance.
I'd prefer the first option, but since for my applications I don't need
things like GlobalInitScript and ChildInitScript other possibilities are
equally good.
--
Valerio Gionco [[EMAIL PROTECTED]]
MOST s.r.l. Via Bezzecca, 9 - 10131 Torino
************************************************************************
"Life's not fair, but the root password helps."
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
