[ http://issues.apache.org/jira/brows...ON-137?page=all ]

Graham Dumpleton updated MODPYTHON-137:
---------------------------------------

Attachment: grahamd_20060228_MP137_1.diff

Attached "grahamd_20060228_MP137_1.diff" containing proposed changes.

> Add req.server.get_options() for obtain PythonOption values set at global 
level.
> --------------------------------------------------------------------------
------
>
>          Key: MODPYTHON-137
>          URL: http://issues.apache.org/jira/browse/MODPYTHON-137
>      Project: mod_python
>         Type: New Feature
>   Components: core
>     Versions: 3.3
>     Reporter: Graham Dumpleton
>     Assignee: Graham Dumpleton
>      Fix For: 3.3
>  Attachments: grahamd_20060228_MP137_1.diff
>
> The req.server.get_config() member seems like it is supposed to allow acce
ss to values of configuration directives set at global context. It seems tho
ugh to have a few problems with it though. See MODPYTHON-133 and MODPYTHON-1
34.
> Regardless of that, it seems it may be appropriate to provide an equivalent for Py
thonOption directive settings. Specifically req.server.get_options(). This would ret
urn a table object giving all PythonOption value settings performed at global scope.
 Th
is would be useful where a value needs to be set globally in one place and not be overridabl
e in more constrained configuration containers.
> This might for example be used as a way or allowing the mutex directory to
 be specified in the Apache configuration as well as as a "configure" comman
d line option. See MODPYTHON-131.
> See commentary along with some patches in:
>   http://www.mail-archive.com/python-...g/msg01295.html

[ Post a follow-up to this message ]