On Wed, Dec 3, 2008 at 11:45 AM, SteveB <[EMAIL PROTECTED]> wrote:
> I've had positive experiences with the standalone CherryPy webserver
> Although I can't prove it, I'm suspicious that the problem may be that
> Django is not thread safe.  Can anyone state for a fact that it is
> safe to use Django with a multi-threaded webserver? If not, then multi-
> threaded webservers like the CherryPy server are not really candidates
> for use with Django.

No-one can state this for a fact because, even though many people (and
this is where I remind everyone that it's often a good idea to search
the archives before posting, especially for frequently-asked questions
like this one) use Django with thread- as opposed to process-based
server solutions without reporting thread-safety issues, it's simply
impossible to state, unequivocally, that "everything you will ever do
involving Django will be 100% thread safe". This should, incidentally,
be fairly clear from the fact that Django offers you numerous ways to
work with, e.g., mutable stateful objects, such that Django itself
doesn't do anything unsafe with them, but you (and by implication,
your code) quite easily can if you're not careful.

In other words, the answer is "to the best of anyone's knowledge,
Django does not have issues running in threaded servers, and if/when
bugs are found which contradict that we fix them". But there isn't and
never will be a categorical assurance that Django is provably 100%
threadsafe or that there won't from time to time be a bug that needs
to be fixed.


-- 
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@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-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to