#3357: Make Django's server optionally multithreaded
------------------------------------------------+---------------------------
Reporter: [email protected] | 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 jaylett):
As per the previous suggestion, see
<http://github.com/jaylett/django_concurrent_test_server/tree/master>, a
very simple (and in some ways utterly evil) app that does this, based on
this patch and the `runserver` command; hence, consider it under the same
license as Django itself.
Drop in `INSTALLED_APPS`, set either `USE_MULTITHREADED_SERVER` or
`USE_MULTIFORKED_SERVER` to True, and `./manage.py runconcurrentserver`.
No warranty, but works for me on the basis of a couple of hour's use
(still several times longer than it took to write). Use the forking
version if threads scare you or you know your user code isn't thread safe.
--
Ticket URL: <http://code.djangoproject.com/ticket/3357#comment:24>
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 [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
-~----------~----~----~----~------~----~------~--~---
