| Graham Dumpleton (JIRA) 2006-03-15, 7:46 am |
| [ http://issues.apache.org/jira/brows...ON-144?page=all ]
Graham Dumpleton resolved MODPYTHON-144:
----------------------------------------
Fix Version: 3.3
Resolution: Fixed
Problem with apache.main_server not always being main server object fixed by having python_init() cache it in global variable and at point server object being supplied to apache.init(), that value being supplied instead of that passed down from calling fu
nctions. The issue of which server object should be used when logging messages left for another time.
> Make apache._server/apace._interpreter part of public API.
> ----------------------------------------------------------
>
> Key: MODPYTHON-144
> URL: http://issues.apache.org/jira/browse/MODPYTHON-144
> Project: mod_python
> Type: Improvement
> Components: core
> Reporter: Graham Dumpleton
> Assignee: 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".
|