#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 mrmachine):
I don't understand the resistence. Streaming HttpResponse functionality
has been in trunk for around 2 years now. All I'm suggesting is that we
fix certain middleware that ships with Django to work with the streaming
functionality that's already present in trunk where possible and
appropriate - e.g. GZip, ETag, etc., and to add a public attribute to
`HttpResponse` to aid the conditional execution of middleware code.
If there are certain middleware that cannot work with dynamic content
generators, they continue to work as they do now. If there are certain
handlers (WSGI) which don't at present work without a Content-Length
header, they continue to work as they do now. Middleware authors can
continue to develop middleware without even being aware that anything has
changed. Existing 3rd party middleware will continue to work as it does
now. This should be backwards compatible.
I don't see how what's been added (essentially just skipping certain
middleware functionality if a generator was used, or being able to replace
an existing generator with a new one) would cause any of the numerous
complications you mention that aren't already and haven't already been
present for the past 2 years.
--
Ticket URL: <http://code.djangoproject.com/ticket/7581#comment:7>
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
-~----------~----~----~----~------~----~------~--~---
