From 7fa5ec5b1a89a8f549ba775081f46206b6658a38 Mon Sep 17 00:00:00 2001 From: Anna Henningsen Date: Fri, 23 Mar 2018 12:54:48 +0100 Subject: [PATCH] doc: remove confusing note about child process stdio MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit It’s not obvious what the paragraph is supposed to say. In particular, whether and what kind of buffering mechanism a process uses for its stdio streams does not affect that, in general, no guarantees can be made about when it consumes data that was sent to it. --- doc/api/child_process.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/doc/api/child_process.md b/doc/api/child_process.md index 09e43b2bd47d7a..6def24c8a571b0 100644 --- a/doc/api/child_process.md +++ b/doc/api/child_process.md @@ -33,10 +33,6 @@ stdout in excess of that limit without the output being captured, the child process will block waiting for the pipe buffer to accept more data. This is identical to the behavior of pipes in the shell. Use the `{ stdio: 'ignore' }` option if the output will not be consumed. -It is possible to stream data through these pipes in a non-blocking way. Note, -however, that some programs use line-buffered I/O internally. While that does -not affect Node.js, it can mean that data sent to the child process may not be -immediately consumed. The [`child_process.spawn()`][] method spawns the child process asynchronously, without blocking the Node.js event loop. The [`child_process.spawnSync()`][]