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:36:32 UTC

[jira] Closed: (MODPYTHON-144) Make apache._server/apace._interpreter part of public API.

     [ https://issues.apache.org/jira/browse/MODPYTHON-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Graham Dumpleton closed MODPYTHON-144.
--------------------------------------


> Make apache._server/apace._interpreter part of public API.
> ----------------------------------------------------------
>
>                 Key: MODPYTHON-144
>                 URL: https://issues.apache.org/jira/browse/MODPYTHON-144
>             Project: mod_python
>          Issue Type: Improvement
>          Components: core
>            Reporter: Graham Dumpleton
>         Assigned To: Graham Dumpleton
>             Fix For: 3.3
>
>
> Within the mod_python.apache module there exists two private variables called "_server" and "_interpreter". These are initialised when an interpreter is first created. The variables are set to be an instance of the mod_python "serverobject" and the name of the interpreter. In effect, these would be the same as are available to a request handler as "req.server" and "req.interpreter".
> The problem with those in the "req" object is that they are only available to the request handler. If these variables in the "mod_python.apache" module are made part of the public API, they would then be accessible by any code. Since "server.get_options()" now exists and "server.get_config()" works properly, making these public would allow code running at global scope when a module is being imported to consult the server level config and/or options to customise their runtime behavour.
> Thus, proposed that these variables be renamed to "apache.server" and "apache.interpreter".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.