#36293: GZipMiddleware buffers streaming responses
-------------------------------------+-------------------------------------
Reporter: huoyinghui | Owner: Farhan
| Ali
Type: Bug | Status: closed
Component: HTTP handling | Version: dev
Severity: Normal | Resolution: fixed
Keywords: gzip flush | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"12bb16da8fbadac34e2de318cc79d7d765f35a96" 12bb16d]:
{{{#!CommitTicketReference repository=""
revision="12bb16da8fbadac34e2de318cc79d7d765f35a96"
Fixed #36293 -- Avoided buffering streaming responses in GZipMiddleware.
This avoids latency and/or blocking.
The example of streaming a CSV file was rewritten to employ batching for
greater efficiency in all layers (db, HTTP, etc.). The improved
performance from batching should outweigh the drag introduced by an
additional byte for each flush.
Co-authored-by: huoyinghui <[email protected]>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36293#comment:23>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019cd29d8669-97e121ca-1c14-4786-830f-ac415f1dd79c-000000%40eu-central-1.amazonses.com.
