[jira] Assigned: (MODPYTHON-137) Add req.server.get_options() for obtain PythonOption values set at global level.

["Graham Dumpleton (JIRA)" <ji...@apache.org>]

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

Graham Dumpleton reassigned MODPYTHON-137:
------------------------------------------

    Assign To: Graham Dumpleton

> 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

>
> The req.server.get_config() member seems like it is supposed to allow access to values of configuration directives set at global context. It seems though to have a few problems with it though. See MODPYTHON-133 and MODPYTHON-134.
> Regardless of that, it seems it may be appropriate to provide an equivalent for PythonOption directive settings. Specifically req.server.get_options(). This would return a table object giving all PythonOption value settings performed at global scope. This would be useful where a value needs to be set globally in one place and not be overridable 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" command line option. See MODPYTHON-131.
> See commentary along with some patches in:
>   http://www.mail-archive.com/python-dev@httpd.apache.org/msg01295.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira