[Soap-Python] gist: 1242760 Unable to run with Django

[Michael Wood]

On 14 March 2012 13:51, azurIt <azurit at pobox.sk> wrote:
>
>>See this for example:
>>
>>http://stackoverflow.com/questions/3405533/problem-using-wsgiapplicationgroup-global-in-apache-configuration
>
> Hah, this is because that user don't understand how mod_wsgi works. Of course that this happened cos he used the same WSGI process and the same application group for all sites. It's his fault and it's not caused by %{GLOBAL} usage. You should:
> 1.) use different application group for _every_ site/application
> 2.) if (1) is not possible (for example, all sites needs to use lxml so all of them needs to run in %{GLOBAL}), use different wsgi process for _every_ such site/application

Of course, but my point is it's not enough to tell someone "Just use
WSGIApplicationGroup %{GLOBAL}" :)  They might also need to use daemon
processes.

>>>>Another possible solution is to use WSGIDaemonProcess as mentioned in
>>>>the article that Burak linked to.
>>>
>>> This is not true. You have to use %{GLOBAL} also when using WSGIDaemonProcess. If you are running several applications using lxml, create several WSGI processes (one per app).
>>
>>OK, it seems you would need WSGIApplicationGroup (but it's not clear
>>to me that it MUST be %{GLOBAL}).
>
> Yes, it MUST be, trust me.

Yes, I see now.

-- 
Michael Wood <esiotrot at gmail.com>