From 9bccd72b7bb1a246a7af8a667062e78acd580d0a Mon Sep 17 00:00:00 2001 From: Tim Kuijsten Date: Tue, 24 May 2016 14:15:16 +0200 Subject: [PATCH] doc: buffers are not sent over IPC with a socket If a socket is sent to a child, any data that is buffered in the socket will not be sent to the child. The child will only receive data from the socket that is sent after the child has the socket. --- doc/api/child_process.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/api/child_process.md b/doc/api/child_process.md index dab853c0bfff8c..b7e5286c51bdba 100644 --- a/doc/api/child_process.md +++ b/doc/api/child_process.md @@ -856,7 +856,8 @@ Applications should avoid using such messages or listening for The optional `sendHandle` argument that may be passed to `child.send()` is for passing a TCP server or socket object to the child process. The child will receive the object as the second argument passed to the callback function -registered on the [`process.on('message')`][] event. +registered on the [`process.on('message')`][] event. Any data that is received +and buffered in the socket will not be sent to the child. The `options` argument, if present, is an object used to parameterize the sending of certain types of handles. `options` supports the following