#3357: Make Django's server optionally multithreaded
------------------------------------------------+---------------------------
Reporter: treborhud...@gmail.com | Owner: adrian
Status: closed | Milestone:
Component: django-admin.py runserver | Version: SVN
Resolution: wontfix | Keywords: post10
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------------------+---------------------------
Comment (by trevorcroft):
Allowing something like:
manage.py runthreadedserver
Is logically equivalent to allowing something like:
manage.py runserver
I think everyone will agree that you should keep runserver in django,
therefore everyone (who is logical) would agree you could have
runthreadedserver.
The arguments for disallowing one are identical to disallowing the other
(fear of stupid users abusing it, and the fact that issues arise during
development that are not real issues), and the arguments for allowing one
are identical for allowing the other (its a great development tool).
--
Ticket URL: <http://code.djangoproject.com/ticket/3357#comment:25>
Django <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 django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
