On 9/25/07, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > > Can we please somehow settle this issue once and for all. I have tried > to get discussions going on this issue in the past but have got > minimal feedback. I thought that too a degree it had been determined > that multithreaded servers were okay, although users should though > ensure there own code is multithread safe, but now again someone is > saying that Django itself is not multithread safe. :-(
I talked with Jacob about this quite a while ago and he told me that Django was not originally written to be threadsafe. The only threading problems I remember hearing about were with the database connections, and those issues were fixed in #1442 [1]. To my knowledge, there has never been any review of the code to check for other possible sticky spots. I used to deploy Django on Windows and never had any threading problems, but the sites were mostly low traffic, internal, and probably not good candidates for exposing problems. In short, Django was not *designed* to be threadsafe, but any obvious problems that I'm aware of have been fixed. YMMV. Joseph [1] http://code.djangoproject.com/ticket/1442 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
