Menu
I just want to attach some variables to my sockets, but I don't understand the .get and .set methods. They both have a third argument for a callback. Can this be omitted? What is it for?! Does the callback itself intherit arguments?
My best guess is that it's there for when socket.io isn't using memory store but is saving this stuff somewhere else and needs an error checking callback.
socket.on('set nickname', function (name) {
socket.set('nickname', name, function (arguments) {
doSomethingMysterious();
});
I'm using socket.io 0.9.x
The function is defined in socket.js
/**
* Stores data for the client.
*
* @api public
*/
Socket.prototype.set = function (key, value, fn) {
this.store.set(key, value, fn);
return this;
};
996
Event CallbacksThe socketio. Server. emit() method has an optional callback argument that can be set to a callable. If this argument is given, the callable will be invoked after the client has processed the event, and any values returned by the client will be passed as arguments to this function.
You can check the socket. connected property: var socket = io. connect(); console.
socket-io. client is the code for the client-side implementation of socket.io. That code may be used either by a browser client or by a server process that is initiating a socket.io connection to some other server (thus playing the client-side role in a socket.io connection).
In the first case, the Socket will automatically try to reconnect, after a given delay.
The get and set functions on the socket object were removed in version 1.x. The proper way to store and retrieve values now is through properties on the socket object, like so:
socket.on('set nickname', function (name) {
socket.nickname = name;
});
As seen on the example code from the official repo.
176
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
