#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 huoyinghui):
Replying to [comment:5 Carlton Gibson]:
This is a good suggestion—it’s simple to implement and avoids having the
real-time performance of the SSE request blocked by compress_sequence. I
accept it.
I think the significance of this issue lies in the fact that when users
use Django to develop SSE requests, they may experience sudden blocking.
However, it’s not directly caused by their own actions, making it hard to
understand and debug.
Perhaps documentation can be added to explain how Django handles SSE
responses. To avoid blocking, users need to configure response["Content-
Encoding"] == "identity".
--
Ticket URL: <https://code.djangoproject.com/ticket/36293#comment:8>
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/0107019613ec1ec2-829e5396-f98c-4a12-96b4-719c3dfde7e7-000000%40eu-central-1.amazonses.com.
