Lines Matching refs:_writev

616 all to `writable._writev()`, if present. This prevents a head-of-line blocking
619 `writable._writev()` may have an adverse effect on throughput.
621 See also: [`writable.uncork()`][], [`writable._writev()`][stream-_writev].
3404 …            | [`Writable`][]  | [`_write()`][stream-_write], [`_writev()`][stream-_writev], [`_fin…
3405 …   | [`_read()`][stream-_read], [`_write()`][stream-_write], [`_writev()`][stream-_writev], [`_fin…
3452 constructor and implement the `writable._write()` and/or `writable._writev()`
3500     [`stream._writev()`][stream-_writev] method.
3632     description: _write() is optional when providing _writev().
3648 [`writable._writev()`][stream-_writev] method to send data to the underlying
3668 data at once, the `writable._writev()` method should be implemented.
3681 #### `writable._writev(chunks, callback)`
3698 The `writable._writev()` method may be implemented in addition or alternatively
3701 from previous writes, `_writev()` will be called instead of `_write()`.
3703 The `writable._writev()` method is prefixed with an underscore because it is
3742 [`writable._writev()`][] and [`writable._final()`][] methods must be propagated
4792 [`writable._writev()`]: #writable_writevchunks-callback
4814 [stream-_writev]: #writable_writevchunks-callback