Skip to content

Commit

Permalink
doc: Remove mention of child.send 'track' option
Browse files Browse the repository at this point in the history
Will be removed very soon.  No point making it public.
  • Loading branch information
isaacs committed Jan 18, 2013
1 parent 01a4be4 commit ee2fd79
Showing 1 changed file with 3 additions and 9 deletions.
12 changes: 3 additions & 9 deletions doc/api/child_process.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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:

Expand Down Expand Up @@ -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
Expand Down

0 comments on commit ee2fd79

Please sign in to comment.