>> 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.
>
Well i don't see much reasons why NOT use daemon processes. It's much more
flexible and faster and it's like some kind of python application server which
is cool. If you are running inside apache processes, everything must be
reinitialized with every reuqest.
azur
_______________________________________________
Soap mailing list
[email protected]
http://mail.python.org/mailman/listinfo/soap
