Jacob states in Ticket #3357 [1] that Django were far from being
thread-safe. But on the other side, Django is able to run as threaded
fastcgi-server (at least with the right backend module version ...)
Isn't this a contradiction?
References:
[1] http://code.djangoproject.com/ticket/3357#comment:7
Michael
--
noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg -
Tel +49-911-9352-0 - Fax +49-911-9352-100
http://www.noris.de - The IT-Outsourcing Company
Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel, Hansjochen Klenk -
Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689
> is able to run as threaded
> fastcgi-server
i think this part is the one where we have to be more exact.
does that mean that : "it is guaranteed to work with a threaded
fastcgi-server"? or more like "i have been using it with a threaded
fastcgi-server, and had no problems for 2 months" ?
gabor
This is strange... Known thread-safety bugs (with db backends mostly)
were fixed long ago, even before magic-removal. I used to run Django
under Apache with worker-mpm without problems.
Jacob could you elaborate?
* good for local testing that more closely resembles a real hosting
environment (eg: with AJAX testing)
* for the development server only
* and disabled by default
you'd think it would be an easy inclusion. I'd like to know more too.
-Rob
just for your information, I've reopened the ticket, asking Jacob for
details about Django being not thread-safe.
http://code.djangoproject.com/ticket/3357#comment:8
Michael