[ http://issues.apache.org/jira/brows...237
0492 ]

Graham Dumpleton commented on MODPYTHON-144:
--------------------------------------------

It is back to apache.main_server after all. This is because although get_opt
ions() returns same for req.connection.base_server and apache.main_server, o
ther attributes are different. For example, server_hostname is an IP address
 for apache.main_server and
the actual virtual host name for req.connection.base_server. Thus distinctio
n is important.

> 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

>
> Within the mod_python.apache module there exists two private variables called "_se
rver" 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 n
ame
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_opti
ons
()" now exists and "server.get_config()" works properly, making these public would allow cod
e 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.inte
rpreter".

[ Post a follow-up to this message ]