On 14 March 2012 13:31, Michael Wood <[email protected]> wrote:
> On 14 March 2012 13:11, azurIt <[email protected]> wrote:
>>
>>>That's not quite true.
>>>
>>>Using WSGIApplicationGroup %{GLOBAL} is one possible solution, but it
>>>can also cause problems.
>>
>> What problems?
>
> See this for example:
>
> http://stackoverflow.com/questions/3405533/problem-using-wsgiapplicationgroup-global-in-apache-configuration
>
>>>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}).
It seems that %{GLOBAL} is the way to go with WSGIDaemonProcess too:
http://stackoverflow.com/questions/5021424/mod-wsgi-daemon-mode-wsgiapplicationgroup-and-python-interpreter-separation
So the safest option seems to use both, but you might be able to get
away with only WSGIApplicationGroup %{GLOBAL} depending on the
circumstances.
--
Michael Wood <[email protected]>
_______________________________________________
Soap mailing list
[email protected]
http://mail.python.org/mailman/listinfo/soap
