doc: Note that zlib.flush acts after pending writes#6172
doc: Note that zlib.flush acts after pending writes#6172addaleax wants to merge 2 commits intonodejs:masterfrom
Conversation
|
LGTM |
|
@jasnell Nah, I’m happy to add stuff to this PR. |
|
Also, 👍 on that an example for |
Describe that `zlib.flush()` may wait for pending writes and until output is being read from the stream.
61615ca to
5a84875
Compare
|
Updated this with a bit more explanation that’s specific to the situation in #3782. |
|
@addaleax +1 .. that change works for me! if there's a concise example that can illustrate the point, then awesome. If not, I'm good with this landing as is. |
|
I’ll sleep over that, but maybe it’s just best noted as a comment in a generic |
|
@nodejs/documentation |
|
Example would be nice if you get one together. In any case LGTM. |
Add a full example using `zlib.flush()` for the common use case of writing partial compressed HTTP output to the client.
|
@eljefedelrodeodeljefe Was literally finishing a first take at an example when you wrote that 😄 Would love to hear what you think of it! |
|
Thought so. Being in the same timezone leads to concurrent working apparently. :) I am a little foreign to |
|
@eljefedelrodeodeljefe Keep in mind that people who are foreign to the specifics are precisely the target groups of the docs, so any questions or suggestions are greatly appreciated! :) |
|
I like it. Thank you very much. LGTM |
Add a full example using `zlib.flush()` for the common use case of writing partial compressed HTTP output to the client. PR-URL: #6172 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
Add a full example using `zlib.flush()` for the common use case of writing partial compressed HTTP output to the client. PR-URL: #6172 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
Add a full example using `zlib.flush()` for the common use case of writing partial compressed HTTP output to the client. PR-URL: #6172 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
Describe that `zlib.flush()` may wait for pending writes and until output is being read from the stream. Fixes: nodejs#3782 PR-URL: nodejs#6172 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
Add a full example using `zlib.flush()` for the common use case of writing partial compressed HTTP output to the client. PR-URL: nodejs#6172 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
Add a full example using `zlib.flush()` for the common use case of writing partial compressed HTTP output to the client. PR-URL: #6172 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
Add a full example using `zlib.flush()` for the common use case of writing partial compressed HTTP output to the client. PR-URL: #6172 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
Add a full example using `zlib.flush()` for the common use case of writing partial compressed HTTP output to the client. PR-URL: #6172 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
Checklist
Affected core subsystem(s)
doc
Description of change
Describe that
zlib.flush()may wait for pending writes. This was discussed a bit in #3782; and although it’s not really related to the original issue report there, the addition probably gives off the right impression, i.e. thatflush()is not as immediate as it may sound.