From ee2fd79e434ed7096193602e614bccc075bac849 Mon Sep 17 00:00:00 2001 From: isaacs Date: Fri, 18 Jan 2013 10:17:26 -0800 Subject: [PATCH] doc: Remove mention of child.send 'track' option Will be removed very soon. No point making it public. --- doc/api/child_process.markdown | 12 +++--------- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/doc/api/child_process.markdown b/doc/api/child_process.markdown index 343030d..596c3c6 100644 --- a/doc/api/child_process.markdown +++ b/doc/api/child_process.markdown @@ -124,11 +124,10 @@ process may not actually kill it. `kill` really just sends a signal to a proces See `kill(2)` -### child.send(message, [sendHandle], [options]) +### child.send(message, [sendHandle]) * `message` {Object} * `sendHandle` {Handle object} -* `options` {Object} When using `child_process.fork()` you can write to the child using `child.send(message, [sendHandle])` and messages are received by @@ -167,12 +166,7 @@ The `sendHandle` option to `child.send()` is for sending a TCP server or socket object to another process. The child will receive the object as its second argument to the `message` event. -The `options` object may have the following properties: - - * `track` - Notify master process when `sendHandle` will be closed in child - process. (`false` by default) - -**send server object** +#### Example: sending server object Here is an example of sending a server: @@ -200,7 +194,7 @@ And the child would the receive the server object as: Note that the server is now shared between the parent and child, this means that some connections will be handled by the parent and some by the child. -**send socket object** +#### Example: sending socket object Here is an example of sending a socket. It will spawn two children and handle connections with the remote address `74.125.127.100` as VIP by sending the -- 2.7.4