socket.localAddress The string representation of the local IP address the remote client is connecting on. For example, if you are listening on '0.0.0.0' and the client connects on '192.168.1.1', the value would be '192.168.1.1'.

socket.destroy() Ensures that no more I/O activity happens on this socket. Only necessary in case of errors (parse error or so).

socket.connect(options[, connectListener]) Opens the connection for a given socket. For TCP sockets, options argument should be an object which specifies: port: Port the client should connect to (Required). host: Host the client should connect to. Defaults to 'localhost'. localAddress: Local interface to bind to for network connections. localPort: Local port to bind to for network connections. family : Version of IP stack. Defaults to 4. lookup : Custom lookup function. Defaults to

socket.bufferSize 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. 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). The consequence of this internal buffe

socket.bytesRead The amount of received bytes.

socket.bytesWritten The amount of bytes sent.

server.unref() Calling unref on a server will allow the program to exit if this is the only active server in the event system. If the server is already unrefd calling unref again will have no effect. Returns server.

socket.address() Returns the bound address, the address family name and port of the socket as reported by the operating system. Returns an object with three properties, e.g. { port: 12346, family: 'IPv4', address: '127.0.0.1' }

server.maxConnections Set this property to reject connections when the server's connection count gets high. It is not recommended to use this option once a socket has been sent to a child with child_process.fork().

server.listen(handle[, backlog][, callback]) handle <Object> backlog <Number> callback <Function> The handle object can be set to either a server or socket (anything with an underlying _handle member), or a {fd: <n>} object. This will cause the server to accept connections on the specified handle, but it is presumed that the file descriptor or handle has already been bound to a port or domain socket. Listening on a file descriptor is not supported on Windows.