diff options
Diffstat (limited to 'doc/api/net.markdown')
| -rw-r--r-- | doc/api/net.markdown | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/api/net.markdown b/doc/api/net.markdown index adc1d97053..1c8b71627d 100644 --- a/doc/api/net.markdown +++ b/doc/api/net.markdown @@ -147,7 +147,7 @@ would be to wait a second and then try again. This can be done with } }); -(Note: All sockets in io.js set `SO_REUSEADDR` already) +(Note: All sockets in Node.js set `SO_REUSEADDR` already) ### server.listen(path[, callback]) @@ -324,7 +324,7 @@ following this event. See example in discussion of `server.listen`. This object is an abstraction of a TCP or local socket. `net.Socket` instances implement a duplex Stream interface. They can be created by the -user and used as a client (with `connect()`) or they can be created by io.js +user and used as a client (with `connect()`) or they can be created by Node.js and passed to the user through the `'connection'` event of a server. ### new net.Socket([options]) @@ -388,7 +388,7 @@ with options either as either `{port: port, host: host}` or `{path: path}`. `net.Socket` has the property that `socket.write()` always works. This is to help users get up and running quickly. The computer cannot always keep up with the amount of data that is written to a socket - the network connection -simply might be too slow. io.js will internally queue up the data written to a +simply might be too slow. Node.js will internally queue up the data written to a socket and send it out over the wire when it is possible. (Internally it is polling on the socket's file descriptor for being writable). |