| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
1 parent 91a1177 commit 5a15cb8
1 file changed
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -546,8 +546,8 @@ The `writable.uncork()` method flushes all data buffered since | |||
| 546 | 546 | [`stream.cork()`][] was called. | |
| 547 | 547 | ||
| 548 | 548 | When using [`writable.cork()`][] and `writable.uncork()` to manage the buffering | |
| 549 | - of writes to a stream, it is recommended that calls to `writable.uncork()` be | ||
| 550 | - deferred using `process.nextTick()`. Doing so allows batching of all | ||
| 549 | + of writes to a stream, defer calls to `writable.uncork()` using | ||
| 550 | + `process.nextTick()`. Doing so allows batching of all | ||
| 551 | 551 | `writable.write()` calls that occur within a given Node.js event loop phase. | |
| 552 | 552 | ||
| 553 | 553 | ```js | |
@@ -713,7 +713,7 @@ stop until the [`'drain'`][] event is emitted. | |||
| 713 | 713 | While a stream is not draining, calls to `write()` will buffer `chunk`, and | |
| 714 | 714 | return false. Once all currently buffered chunks are drained (accepted for | |
| 715 | 715 | delivery by the operating system), the `'drain'` event will be emitted. | |
| 716 | - It is recommended that once `write()` returns false, no more chunks be written | ||
| 716 | + Once `write()` returns false, do not write more chunks | ||
| 717 | 717 | until the `'drain'` event is emitted. While calling `write()` on a stream that | |
| 718 | 718 | is not draining is allowed, Node.js will buffer all written chunks until | |
| 719 | 719 | maximum memory usage occurs, at which point it will abort unconditionally. | |
@@ -873,10 +873,9 @@ to consume data from a single stream. Specifically, using a combination | |||
| 873 | 873 | of `on('data')`, `on('readable')`, `pipe()`, or async iterators could | |
| 874 | 874 | lead to unintuitive behavior. | |
| 875 | 875 | ||
| 876 | - Use of the `readable.pipe()` method is recommended for most users as it has been | ||
| 877 | - implemented to provide the easiest way of consuming stream data. Developers that | ||
| 878 | - require more fine-grained control over the transfer and generation of data can | ||
| 879 | - use the [`EventEmitter`][] and `readable.on('readable')`/`readable.read()` | ||
| 876 | + `readable.pipe()` provides the easiest way to consume stream data. Developers | ||
| 877 | + that require more fine-grained control over the transfer and generation of data | ||
| 878 | + can use the [`EventEmitter`][] and `readable.on('readable')`/`readable.read()` | ||
| 880 | 879 | or the `readable.pause()`/`readable.resume()` APIs. | |
| 881 | 880 | ||
| 882 | 881 | #### Class: `stream.Readable` | |
| Back | FazBrowse Home | New Git URL |
0 commit comments