On 29 syys, 07:45, Tai Lee <real.hu...@mrmachine.net> wrote:
> Docs have been added (patch should be complete now) and pull request has
> been opened, at Anssi's request.
>
> https://groups.google.com/d/topic/django-developers/RrNPfuJxnlM/discu...

To me it seems the use of streaming responses in static file serving
will cause problems for upgraders. If using 3rd party middleware
accessing .content, then the following will happen:
  - The static files will now automatically use streaming responses
  - The middleware will be applied to the static file responses, too
  - There is no .content for streaming responses -> problems

The problem stems from using the new streaming response by default in
Django. If it wasn't used, then there would be no problems for
upgrades.

I think we have to put in place something like
BackwardsCompatStreamingResponse - on access of .content raise a
deprecation warning, but still allow .content to work. This could be
used for two releases in static file serving.

Alternate approach is to tell upgraders to wrap non-working middleware
in a subclass skipping the middleware for streaming responses.

 - Anssi

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to