Manager#reconnectionDelayMax(v:Boolean):Manager Sets the reconectionDelayMax option, or returns it if no parameters are passed.

Namespace Represents a pool of sockets connected under a given scope identified by a pathname (eg: /chat). By default the client always connects to /. Events connection / connect. Fired upon a connection. Parameters: Socket the incoming socket.

Manager#reconnectionDelay(v:Boolean):Manager Sets the reconectionDelay option, or returns it if no parameters are passed.

Manager#reconnectionAttempts(v:Boolean):Manager Sets the reconnectionAttempts option, or returns it if no parameters are passed.

For most applications, the transition to 1.0 should be completely seamless and devoid of any hiccups. That said, we’ve done some work to streamline some APIs, and we have changed some internals, so this is a recommended read for most existing users. Authentication differences Socket.io uses middleware now You can give a Socket.io server arbitrary functions via io.use() that are run when a socket is created. Check out this example: var srv = require('http').createServer(); var io = require('sock

Namespace#connected:Object Hash of Socket objects that are connected to this namespace indexed by id.

Manager#reconnection(v:Boolean):Manager Sets the reconnection option, or returns it if no parameters are passed.

IO#Socket Reference to the Socket constructor.

IO#Emitter Reference to the Emitter constructor.

Socket.IO is now completely instrumented by a minimalistic yet tremendously powerful utility called debug by TJ Holowaychuk. Before 1.0, the Socket.IO server would default to logging everything out to the console. This turned out to be annoyingly verbose for many users (although extremely useful for others), so now we default to being completely silent by default. The basic idea is that each module used by Socket.IO provides different debugging scopes that give you insight into the internals. B