On 2011-01-07 16:39:46 -0800, Alex Grönholm said:
I believe allowing wsgi.executor to be either a process pool or a
thread pool is a recipe for disaster. I'm really not sure where to go
from here.
Two solutions:
:: Don't pass an executor to the job such that it can not schedule its
own futures.
:: Mandate a thread pool, not process pool, to avoid deadlocking.
- Alice.
_______________________________________________
Web-SIG mailing list
Web-SIG@python.org
Web SIG: http://www.python.org/sigs/web-sig
Unsubscribe:
http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
