#7581: Middleware accessing HttpResponse.content breaks streaming HttpResponse
objects.
---------------------------------------------+------------------------------
Reporter: mrmachine | Owner: nobody
Status: new | Milestone: post-1.0
Component: Core framework | Version: SVN
Resolution: | Keywords: stream
HttpResponse
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Comment (by ubernostrum):
The more I think about this, the more I'm -1 on it. The complications of
trying to force lazily-evaluated responses are far too numerous (ranging
all the way from resource leaks on the Django side out to things like WSGI
forbidding useful HTTP features which help with this) and the existence of
specialized solutions for doing long-lived HTTP and/or asynchronous stuff
are too plentiful to justify Django special-casing enough stuff to make
this work.
--
Ticket URL: <http://code.djangoproject.com/ticket/7581#comment:6>
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
-~----------~----~----~----~------~----~------~--~---
