This Readme corresponds to the upcoming 1.0 release. Please refer to http://socket.io for the current 0.9.x documentation.
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-client.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', fucntion(){});
});
</script>Socket.IO is a component, which
means you can include it by using require on the browser:
var socket = require('socket.io')('http://localhost');
socket.on('connect', function(){
socket.on('event', function(data){});
socket.on('disconnect', fucntion(){});
});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', fucntion(){});
});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.
connect. Fired upon a succesful connection.connect_error. Fired upon a connection error. Parameters:Objecterror object
connect_timeout. Fired upon a connection timeout.reconnect. Fired upon a successful reconnection. Parameters:Numberreconnection attempt number
reconnect_error. Fired upon a reconnection attempt error. Parameters:Objecterror object
reconnect_failed
connect. Fired upon connecting.error. Fired upon a connection error Parameters:Objecterror data
disconnect. Fired upon a disconnection.
MIT
