You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mod_python-dev@quetz.apache.org by "Graham Dumpleton (JIRA)" <ji...@apache.org> on 2007/04/11 13:32:33 UTC
[jira] Closed: (MODPYTHON-137) Add req.server.get_options() for
obtain PythonOption values set at global level.
[ https://issues.apache.org/jira/browse/MODPYTHON-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Graham Dumpleton closed MODPYTHON-137.
--------------------------------------
> Add req.server.get_options() for obtain PythonOption values set at global level.
> --------------------------------------------------------------------------------
>
> Key: MODPYTHON-137
> URL: https://issues.apache.org/jira/browse/MODPYTHON-137
> Project: mod_python
> Issue Type: New Feature
> Components: core
> Affects Versions: 3.3
> Reporter: Graham Dumpleton
> Assigned To: Graham Dumpleton
> Fix For: 3.3, 3.2.10
>
> Attachments: grahamd_20060228_MP137_1.diff
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.