There are some configuration directives, like Dtcl_Script BeforeScript
that one could quite conceivably wish to use on a per-directory
basis. Currently, this isn't possible, as Dtcl_Script is a
"RSRC_CONF", or, in other words:
* (req_override & RSRC_CONF) => *.conf outside <Directory> or <Location>
(according to http_config.h).
Whereas we really want to be using something like:
* (req_override & OR_OPTIONS) => *.conf anywhere
* and .htaccess when AllowOverride Options
However, the problem is that some of the Dtcl_Script options really
are global, such as GlobalInitScript and ChildInitScript - they
shouldn't be set on a per-directory basis!
So, there are a couple of options:
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.
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.
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.
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.
--
David N. Welton
Free Software: http://people.debian.org/~davidw/
Apache Tcl: http://tcl.apache.org/
Personal: http://www.efn.org/~davidw/
Work: http://www.innominate.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
