On 20 elo, 22:21, Alex Gaynor <[email protected]> wrote: > My inclination is that we should kill .content entirely, middleware that > wants to rewrite the response will have two choices: > > 1) explicitly evaluate the entire response, and return a new HttpResponse > object > 2) return s anew HttpResponse object that has a generator that iteratively > evaluates the previous one and rewrite it incrementally.
+1 The above still leaves one part of the problem unsolved. If you have a middleware that wants to access the content of the response for some reason, it has no way to know if the content is too large to be accessed safely. I do think we need in addition some way to tell the middleware that the content is too large to be handled at all in Python. As an addition to the already suggested ideas maybe a view decorator could work? - Anssi -- You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en.
