0
0
mirror of https://github.com/nodejs/node.git synced 2024-11-29 23:16:30 +01:00
nodejs/doc/api/net.markdown

398 lines
12 KiB
Markdown
Raw Normal View History

## net
The `net` module provides you with an asynchronous network wrapper. It contains
methods for creating both servers and clients (called streams). You can include
this module with `require("net");`
2011-03-02 19:32:13 +01:00
### net.createServer([options], [connectionListener])
Creates a new TCP server. The `connectionListener` argument is
automatically set as a listener for the `'connection'` event.
2011-03-02 19:32:13 +01:00
`options` is an object with the following defaults:
{ allowHalfOpen: false
}
If `allowHalfOpen` is `true`, then the socket won't automatically send FIN
packet when the other end of the socket sends a FIN packet. The socket becomes
non-readable, but still writable. You should call the end() method explicitly.
See `'end'` event for more information.
### net.createConnection(arguments...)
2011-01-05 20:53:56 +01:00
Construct a new socket object and opens a socket to the given location. When
the socket is established the `'connect'` event will be emitted.
The arguments for this method change the type of connection:
* `net.createConnection(port, [host])`
Creates a TCP connection to `port` on `host`. If `host` is omitted, `localhost`
will be assumed.
* `net.createConnection(path)`
Creates unix socket connection to `path`
---
### net.Server
2010-10-28 14:18:16 +02:00
This class is used to create a TCP or UNIX server.
Here is an example of a echo server which listens for connections
on port 8124:
var net = require('net');
var server = net.createServer(function (c) {
c.write('hello\r\n');
c.pipe(c);
2010-10-28 14:18:16 +02:00
});
server.listen(8124, 'localhost');
Test this by using `telnet`:
telnet localhost 8124
To listen on the socket `/tmp/echo.sock` the last line would just be
2010-10-28 14:18:16 +02:00
changed to
server.listen('/tmp/echo.sock');
Use `nc` to connect to a UNIX domain socket server:
nc -U /tmp/echo.sock
`net.Server` is an `EventEmitter` with the following events:
2010-10-28 14:18:16 +02:00
#### server.listen(port, [host], [callback])
2010-10-28 14:18:16 +02:00
Begin accepting connections on the specified `port` and `host`. If the
`host` is omitted, the server will accept connections directed to any
IPv4 address (`INADDR_ANY`).
This function is asynchronous. The last parameter `callback` will be called
when the server has been bound.
2010-11-29 09:20:21 +01:00
One issue some users run into is getting `EADDRINUSE` errors. Meaning
another server is already running on the requested port. One way of handling this
would be to wait a second and the try again. This can be done with
server.on('error', function (e) {
2011-02-04 23:35:14 +01:00
if (e.code == 'EADDRINUSE') {
2010-11-29 09:20:21 +01:00
console.log('Address in use, retrying...');
setTimeout(function () {
server.close();
server.listen(PORT, HOST);
}, 1000);
}
});
(Note: All sockets in Node are set SO_REUSEADDR already)
#### server.listen(path, [callback])
2010-10-28 14:18:16 +02:00
Start a UNIX socket server listening for connections on the given `path`.
This function is asynchronous. The last parameter `callback` will be called
when the server has been bound.
#### server.listenFD(fd)
2010-10-28 14:18:16 +02:00
Start a server listening for connections on the given file descriptor.
This file descriptor must have already had the `bind(2)` and `listen(2)` system
calls invoked on it.
#### server.pause(msecs)
Stop accepting connections for the given number of milliseconds (default is
one second). This could be useful for throttling new connections against
DoS attacks or other oversubscription.
#### server.close()
2010-10-28 14:18:16 +02:00
Stops the server from accepting new connections. This function is
asynchronous, the server is finally closed when the server emits a `'close'`
event.
2010-11-16 05:26:46 +01:00
#### server.address()
Returns the bound address and port of the server as reported by the operating system.
Useful to find which port was assigned when giving getting an OS-assigned address.
Returns an object with two properties, e.g. `{"address":"127.0.0.1", "port":2121}`
2010-11-16 05:26:46 +01:00
Example:
var server = net.createServer(function (socket) {
socket.end("goodbye\n");
});
// grab a random port.
server.listen(function() {
address = server.address();
console.log("opened server on %j", address);
});
#### server.maxConnections
2010-10-28 14:18:16 +02:00
Set this property to reject connections when the server's connection count gets high.
#### server.connections
2010-10-28 14:18:16 +02:00
The number of concurrent connections on the server.
#### Event: 'connection'
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
`function (socket) {}`
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
Emitted when a new connection is made. `socket` is an instance of
`net.Socket`.
2010-10-28 14:18:16 +02:00
#### Event: 'close'
2010-10-28 14:18:16 +02:00
`function () {}`
2010-10-28 14:18:16 +02:00
Emitted when the server closes.
2010-10-28 14:18:16 +02:00
---
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
### net.Socket
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
This object is an abstraction of of a TCP or UNIX socket. `net.Socket`
instances implement a duplex Stream interface. They can be created by the
2010-10-28 14:18:16 +02:00
user and used as a client (with `connect()`) or they can be created by Node
and passed to the user through the `'connection'` event of a server.
2011-01-05 20:53:56 +01:00
`net.Socket` instances are EventEmitters with the following events:
2010-10-28 14:18:16 +02:00
2011-03-10 18:15:05 +01:00
#### new net.Socket([options])
Construct a new socket object.
`options` is an object with the following defaults:
{ fd: null
type: null
allowHalfOpen: false
}
`fd` allows you to specify the existing file descriptor of socket. `type`
specified underlying protocol. It can be `'tcp4'`, `'tcp6'`, or `'unix'`.
About `allowHalfOpen`, refer to `createServer()` and `'end'` event.
2011-01-05 20:53:56 +01:00
#### socket.connect(port, [host], [callback])
#### socket.connect(path, [callback])
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
Opens the connection for a given socket. If `port` and `host` are given,
then the socket will be opened as a TCP socket, if `host` is omitted,
`localhost` will be assumed. If a `path` is given, the socket will be
opened as a unix socket to that path.
2010-10-28 14:18:16 +02:00
Normally this method is not needed, as `net.createConnection` opens the
2011-01-05 20:53:56 +01:00
socket. Use this only if you are implementing a custom Socket or if a
Socket is closed and you want to reuse it to connect to another server.
2010-10-28 14:18:16 +02:00
This function is asynchronous. When the `'connect'` event is emitted the
2011-01-05 20:53:56 +01:00
socket is established. If there is a problem connecting, the `'connect'`
event will not be emitted, the `'error'` event will be emitted with
the exception.
2010-10-28 14:18:16 +02:00
2011-02-25 01:36:43 +01:00
The `callback` parameter will be added as an listener for the 'connect'
event.
2010-10-28 14:18:16 +02:00
2011-01-31 19:41:52 +01:00
#### socket.bufferSize
`net.Socket` has the property that `socket.write()` always works. This is to
help users get up an running quickly. The computer cannot necessarily keep up
with the amount of data that is written to a socket - the network connection simply
might be too slow. Node 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).
The consequence of this internal buffering is that memory may grow. This
property shows the number of characters currently buffered to be written.
(Number of characters is approximately equal to the number of bytes to be
written, but the buffer may contain strings, and the strings are lazily
encoded, so the exact number of bytes is not known.)
Users who experience large or growing `bufferSize` should attempt to
"throttle" the data flows in their program with `pause()` and resume()`.
2011-01-05 20:53:56 +01:00
#### socket.setEncoding(encoding=null)
2010-10-28 14:18:16 +02:00
Sets the encoding (either `'ascii'`, `'utf8'`, or `'base64'`) for data that is
received.
2010-10-28 14:18:16 +02:00
2011-01-05 20:55:24 +01:00
#### socket.setSecure()
2010-10-28 14:18:16 +02:00
2011-01-05 20:55:24 +01:00
This function has been removed in v0.3. It used to upgrade the connection to
SSL/TLS. See the [TLS section](tls.html#tLS_) for the new API.
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
#### socket.write(data, [encoding], [callback])
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
Sends data on the socket. The second parameter specifies the encoding in the
case of a string--it defaults to UTF8 encoding.
2010-10-28 14:18:16 +02:00
Returns `true` if the entire data was flushed successfully to the kernel
buffer. Returns `false` if all or part of the data was queued in user memory.
`'drain'` will be emitted when the buffer is again free.
2010-10-28 14:18:16 +02:00
2010-12-16 00:47:02 +01:00
The optional `callback` parameter will be executed when the data is finally
written out - this may not be immediately.
2011-01-05 20:53:56 +01:00
#### socket.write(data, [encoding], [fileDescriptor], [callback])
For UNIX sockets, it is possible to send a file descriptor through the
2011-01-05 20:53:56 +01:00
socket. Simply add the `fileDescriptor` argument and listen for the `'fd'`
event on the other end.
2011-01-05 20:53:56 +01:00
#### socket.end([data], [encoding])
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
Half-closes the socket. I.E., it sends a FIN packet. It is possible the
2010-12-09 01:04:21 +01:00
server will still send some data.
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
If `data` is specified, it is equivalent to calling `socket.write(data, encoding)`
followed by `socket.end()`.
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
#### socket.destroy()
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
Ensures that no more I/O activity happens on this socket. Only necessary in
case of errors (parse error or so).
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
#### socket.pause()
2010-10-28 14:18:16 +02:00
Pauses the reading of data. That is, `'data'` events will not be emitted.
Useful to throttle back an upload.
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
#### socket.resume()
2010-10-28 14:18:16 +02:00
Resumes reading after a call to `pause()`.
2010-10-28 14:18:16 +02:00
#### socket.setTimeout(timeout, [callback])
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
Sets the socket to timeout after `timeout` milliseconds of inactivity on
the socket. By default `net.Socket` do not have a timeout.
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
When an idle timeout is triggered the socket will receive a `'timeout'`
event but the connection will not be severed. The user must manually `end()`
2011-01-05 20:53:56 +01:00
or `destroy()` the socket.
2010-10-28 14:18:16 +02:00
If `timeout` is 0, then the existing idle timeout is disabled.
2010-10-28 14:18:16 +02:00
The optional `callback` parameter will be added as a one time listener for the `'timeout'` event.
2011-01-05 20:53:56 +01:00
#### socket.setNoDelay(noDelay=true)
2010-10-28 14:18:16 +02:00
Disables the Nagle algorithm. By default TCP connections use the Nagle
algorithm, they buffer data before sending it off. Setting `noDelay` will
2011-01-05 20:53:56 +01:00
immediately fire off data each time `socket.write()` is called.
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
#### socket.setKeepAlive(enable=false, [initialDelay])
2010-10-28 14:18:16 +02:00
Enable/disable keep-alive functionality, and optionally set the initial
2011-01-05 20:53:56 +01:00
delay before the first keepalive probe is sent on an idle socket.
Set `initialDelay` (in milliseconds) to set the delay between the last
data packet received and the first keepalive probe. Setting 0 for
initialDelay will leave the value unchanged from the default
(or previous) setting.
2010-10-28 14:18:16 +02:00
#### socket.address()
Returns the bound address and port of the socket as reported by the operating system.
Returns an object with two properties, e.g. `{"address":"192.168.57.1", "port":62053}`
2011-01-05 20:53:56 +01:00
#### socket.remoteAddress
2010-10-28 14:18:16 +02:00
The string representation of the remote IP address. For example,
`'74.125.127.100'` or `'2001:4860:a005::68'`.
This member is only present in server-side connections.
#### Event: 'connect'
2010-10-28 14:18:16 +02:00
`function () { }`
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
Emitted when a socket connection successfully is established.
See `connect()`.
2010-10-28 14:18:16 +02:00
#### Event: 'data'
2010-10-28 14:18:16 +02:00
`function (data) { }`
2010-10-28 14:18:16 +02:00
Emitted when data is received. The argument `data` will be a `Buffer` or
2011-01-05 20:53:56 +01:00
`String`. Encoding of data is set by `socket.setEncoding()`.
(See the [Readable Stream](streams.html#readable_Stream) section for more information.)
2010-10-28 14:18:16 +02:00
#### Event: 'end'
2010-10-28 14:18:16 +02:00
`function () { }`
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
Emitted when the other end of the socket sends a FIN packet.
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
By default (`allowHalfOpen == false`) the socket will destroy its file
descriptor once it has written out its pending write queue. However, by
2011-01-05 20:53:56 +01:00
setting `allowHalfOpen == true` the socket will not automatically `end()`
its side allowing the user to write arbitrary amounts of data, with the
2010-12-09 01:04:21 +01:00
caveat that the user is required to `end()` their side now.
2010-10-28 14:18:16 +02:00
#### Event: 'timeout'
2010-10-28 14:18:16 +02:00
`function () { }`
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
Emitted if the socket times out from inactivity. This is only to notify that
the socket has been idle. The user must manually close the connection.
2010-10-28 14:18:16 +02:00
2011-01-05 20:53:56 +01:00
See also: `socket.setTimeout()`
2010-10-28 14:18:16 +02:00
#### Event: 'drain'
2010-10-28 14:18:16 +02:00
`function () { }`
2010-10-28 14:18:16 +02:00
Emitted when the write buffer becomes empty. Can be used to throttle uploads.
2010-10-28 14:18:16 +02:00
#### Event: 'error'
2010-10-28 14:18:16 +02:00
`function (exception) { }`
2010-10-28 14:18:16 +02:00
Emitted when an error occurs. The `'close'` event will be called directly
following this event.
2010-10-28 14:18:16 +02:00
#### Event: 'close'
`function (had_error) { }`
2011-01-05 20:53:56 +01:00
Emitted once the socket is fully closed. The argument `had_error` is a boolean
which says if the socket was closed due to a transmission error.
---
### net.isIP
#### net.isIP(input)
Tests if input is an IP address. Returns 0 for invalid strings,
returns 4 for IP version 4 addresses, and returns 6 for IP version 6 addresses.
#### net.isIPv4(input)
Returns true if input is a version 4 IP address, otherwise returns false.
#### net.isIPv6(input)
Returns true if input is a version 6 IP address, otherwise returns false.
2010-10-28 14:18:16 +02:00