#12091: [PATCH] Support for WSGI applications within Django
-------------------------------+------------------------------------
Reporter: Gustavo | Owner: Gustavo
Type: New feature | Status: closed
Component: HTTP handling | Version: master
Severity: Normal | Resolution: wontfix
Keywords: WSGI | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Changes (by aaugustin):
* status: new => closed
* resolution: => wontfix
Comment:
I'm in favor of keeping this feature outside of Django, for the following
reasons.
1) Embedding WSGI applications in Django isn't the most robust design.
It's much better to dispatch at the WSGI level between Django and other
applications.
2) While it's easy to just make this feature work for simple use cases,
it's very difficult to make the gateway 100% WSGI-compliant (even if the
recently-added `StreamingHttpResponse` could help abide by the buffering
rules). I'm afraid this would add a significant maintainance load, while
benefitting only a few users with non-trivial architectures.
3) There isn't any reason why this needs to live in core, and there are a
few implementations floating in the wild. I have my own implementation of
this too -- I use it in development as a replacement for
`uwsgi.applications`
(http://projects.unbit.it/uwsgi/wiki/ApplicationsDict).
--
Ticket URL: <https://code.djangoproject.com/ticket/12091#comment:10>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
