2008/10/1 Pigletto <[EMAIL PROTECTED]>:
> One more question as I'm a bit confused about WSGIApplicationGroup
> directive. So far I was not using this at all. Does this mean that %
> {GLOBAL} was used implicitly - by default? I only had WSGIProcessGroup
> directives in use.
The default for WSGIApplicationGroup is %{RESOURCE}. This means the
named sub interpreter used is either:
server_hostname|/mount/point
for ports 80/443. Or:
server_hostname:server_port|/mount/point
for other ports.
You can see the value in WSGI environment as mod_wsgi.application_group.
What this means is that by default every WSGI application mounted at
different mount point, whether or not in different virtual hosts, get
a distinct sub interpreter. The mount point here is what SCRIPT_NAME
would be that is passed to application. The server hostname is what
SERVER_NAME is and the port SERVER_PORT.
Thus, applications are by default isolated from each other.
Using %{GLOBAL} forces any request handled in context that directive
is in, to be handled in the first/main Python interpreter. This is
effectively the same Python interpreter instance that command line
code always runs in.
This first/main interpreter results in mod_wsgi.application_group in
WSGI environment being empty string.
Graham
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en
-~----------~----~----~----~------~----~------~--~---
