#3357: Make Django's server optionally multithreaded
--------------------------------------+-------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: closed | Component: django-admin.py
runserver
Version: SVN | Resolution: wontfix
Keywords: | Stage: Ready for
checkin
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------------+-------------------------------------
Comment (by Matthias Urlichs <[EMAIL PROTECTED]>):
Umm, to second what mir said: Some people *need* that feature.
The fix for threading problems (which may or may not still exist) is to
find and fix them, not to make threading harder to use (or worse).
Besides, there are other "quality" deployment scenarios for Django which
depend on threading (e.g. running Django as a WSGI server under Twisted).
People deploying against runserver? Sorry, that's a non-argument. By the
same token, you might want to disallow gigabit network interfaces because
somebody might saturate somebody's DSL with it. (Just to pick an equally-
silly example.)
--
Ticket URL: <http://code.djangoproject.com/ticket/3357#comment:13>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
