#6527: A bug in HttpResponse with iterators
--------------------------------------------------+-------------------------
Reporter: daonb <[email protected]> | Owner: ccahoon
Status: new | Milestone:
Component: HTTP handling | Version: SVN
Resolution: | Keywords: http
iterators
Stage: Fixed on a branch | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------------------+-------------------------
Comment (by mrmachine):
So if/when this hits trunk, we will lose the benefit of not having the
entire iterator (potentially large and time consuming) saved in memory,
which could also potentially cause browser timeouts? If HttpResponse will
have no real support for iterators, why not simply make HttpResponse
require a string argument? Users wanting to pass an iterator can simply
consume it then.
--
Ticket URL: <http://code.djangoproject.com/ticket/6527#comment:18>
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
-~----------~----~----~----~------~----~------~--~---
