Re: [Django] #36293: GZipMiddleware buffers streaming responses (was: Extend `django.utils.text.compress_sequence()` to optionally flush data written to compressed file)

[Django]

#36293: GZipMiddleware buffers streaming responses
-------------------------------+-------------------------------------
Reporter: huoyinghui | Owner: (none)
Type: Bug | Status: closed
Component: HTTP handling | Version: dev
Severity: Normal | Resolution: needsinfo
Keywords: gzip flush | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+-------------------------------------
Changes (by Jacob Walls):

* has_patch: 1 => 0
* stage: Unreviewed => Accepted
* summary:
Extend `django.utils.text.compress_sequence()` to optionally flush
data written to compressed file
=> GZipMiddleware buffers streaming responses
* type: New feature => Bug

Comment:

> So maybe we should rewrite that example, as well as restore the
flushing?

Sounds reasonable to me. The docs suggestion from comment:5 seems like
settling for less, since we'd be giving up the ability to compress
streaming responses, but I'm open to anything I've missed.
--
Ticket URL: <https://code.djangoproject.com/ticket/36293#comment:15>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.