On 21/12/2005, at 3:32 PM, Graham Dumpleton wrote:
Grisha wrote ..
This sounds like a good idea, but it's probably better to push this
off
to
3.3 just to veer on the side of caution.
My $0.02
Grisha
Grisha, do you remember why the following warning is present in
directive_PythonInputFilter() and directive_PythonOutputFilter() of
"mod_python.c".
/* register the filter NOTE - this only works so long as the
directive is only allowed in the main config. For .htaccess we
would have to make sure not to duplicate this */
Having input/output filters be able to be specified in .htaccess
must have been considered, but there must have been some issue
with it that prevented it being done at the time.
Hmmm, looks like it will not be able to be done after all. This is
because registration of a filter by name is done at server scope.
Thus, if done from a .htaccess file in one directory, it will then
be visible in other scopes. The continual registration of the
filter each time a request hits that directory will also cause a
growing use of memory from the server pool (I think). Pity.
I wander though whether one could register a single global hook into
mod_python for filters automatically, and then for configuration of
filters to be managed within mod_python somehow. Anyway, could be an
interesting area for future exploration. Will be interesting to see
how mod_perl might deal with being able to specify filters at .htaccess
level.
Graham
