A standalone build of socket.io-client
is exposed automatically by the
socket.io server as /socket.io/socket.io.js
. Alternatively you can
serve the file socket.io.js
found at the root of this repository.
<script src="/socket.io/socket.io.js"></script>
<script>
var socket = io('http://localhost');
socket.on('connect', function(){
socket.on('event', function(data){});
socket.on('disconnect', function(){});
});
</script>
Socket.IO is compatible with browserify.
Add socket.io-client
to your package.json
and then:
var socket = require('socket.io-client')('http://localhost');
socket.on('connect', function(){
socket.on('event', function(data){});
socket.on('disconnect', function(){});
});
Exposed as the io
namespace in the standalone build, or the result
of calling require('socket.io-client')
.
When called, it creates a new Manager
for the given URL, and attempts
to reuse an existing Manager
for subsequent calls, unless the
multiplex
option is passed with false
.
The rest of the options are passed to the Manager
constructor (see below
for details).
A Socket
instance is returned for the namespace specified by the
pathname in the URL, defaulting to /
. For example, if the url
is
http://localhost/users
, a transport connection will be established to
http://localhost
and a Socket.IO connection will be established to
/users
.
Socket.io protocol revision number this client works with.
Reference to the Socket
constructor.
Reference to the Manager
constructor.
Reference to the Emitter
constructor.
A Manager
represents a connection to a given Socket.IO server. One or
more Socket
instances are associated with the manager. The manager
can be accessed through the io
property of each Socket
instance.
The opts
are also passed to engine.io
upon initialization of the
underlying Socket
.
Options:
reconnection
whether to reconnect automatically (true
)reconnectionDelay
how long to wait before attempting a new
reconnection (1000
)reconnectionDelayMax
maximum amount of time to wait between
reconnections (5000
). Each attempt increases the reconnection by
the amount specified by reconnectionDelay
.timeout
connection timeout before a connect_error
and connect_timeout
events are emitted (20000
)autoConnect
by setting this false, you have to call manager.open
whenever you decide it's appropriateconnect
. Fired upon a successful connection.connect_error
. Fired upon a connection error.
Parameters:
Object
error objectconnect_timeout
. Fired upon a connection timeout.reconnect
. Fired upon a successful reconnection.
Parameters:
Number
reconnection attempt numberreconnect_attempt
. Fired upon an attempt to reconnect.reconnecting
. Fired upon an attempt to reconnect.
Parameters:
Number
reconnection attempt numberreconnect_error
. Fired upon a reconnection attempt error.
Parameters:
Object
error objectreconnect_failed
. Fired when couldn't reconnect within reconnectionAttempts
The events above are also emitted on the individual sockets that
reconnect that depend on this Manager
.
Sets the reconnection
option, or returns it if no parameters
are passed.
Sets the reconnectionAttempts
option, or returns it if no parameters
are passed.
Sets the reconectionDelay
option, or returns it if no parameters
are passed.
Sets the reconectionDelayMax
option, or returns it if no parameters
are passed.
Sets the timeout
option, or returns it if no parameters
are passed.
connect
. Fired upon connecting.error
. Fired upon a connection error
Parameters:
Object
error datadisconnect
. Fired upon a disconnection.reconnect
. Fired upon a successful reconnection.
Parameters:
Number
reconnection attempt numberreconnect_attempt
. Fired upon an attempt to reconnect.reconnecting
. Fired upon an attempt to reconnect.
Parameters:
Number
reconnection attempt numberreconnect_error
. Fired upon a reconnection attempt error.
Parameters:
Object
error objectreconnect_failed
. Fired when couldn't reconnect within reconnectionAttempts
MIT