#36293: Extend `django.utils.text.compress_sequence()` to optionally flush data
written to compressed file
-------------------------------+--------------------------------------
Reporter: huoyinghui | Owner: (none)
Type: New feature | Status: closed
Component: HTTP handling | Version: dev
Severity: Normal | Resolution: needsinfo
Keywords: gzip flush | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Carlton Gibson):
> …so long as we don't introduce additional API…
Just to clarify, I'm not anti more API here ''per se''. Rather, I'd like
to see us be sure we've thought it through before we do that.
(I have a pretty strong suspicion that an ounce of docs would go a long
way here (especially given the identity encoding suggestion above)
> In the case of adding flushing the gzipping triples the response time to
produce a 10% smaller response.
I think there's a typo there somewhere. 🤔 (The numbers as written have
triple response time for ≈double response size, unless I'm failing to read
it right.)
--
Ticket URL: <https://code.djangoproject.com/ticket/36293#comment:12>
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/01070199f625e550-a562ded1-b991-4ed2-828e-33304adc8cfc-000000%40eu-central-1.amazonses.com.
