Socket IO | How to get the client transport type on the serverside?

Question

I need to know what transport method a client is using for some conditional statements on the nodeJS serverside.

Does anyone know how I can get that

Answer 1

As of Socket.IO 1.0:

Client:

socket.on('connect', function() {
    console.log(socket.io.engine.transport.name);
}

Server:

io.sockets.on('connection', function(socket) {
    console.log(socket.conn.transport.name);
}

Answer 2

I believe this will solve your problem. My trick here is to save the transport type on the HTTP Request object once the client connects. You can then pick it up in your callback later. First we tweak the Listener class:

var io = require('socket.io'),
io.Listener.prototype._onConnectionOld = io.Listener.prototype._onConnection;
io.Listener.prototype._onConnection = function(transport, req, res, up, head){
  req.socketIOTransport = transport;  // Take note of the transport type
  this._onConnectionOld.call(this, transport, req, res, up, head);
};

And then below in the body of your app:

var socket = io.listen(app),
socket.on('connection', function(client){
    console.log(client.request.socketIOTransport);  // Lets check that transport
    // ...
});

Hope this helps!

Answer 3

for reference's sake and google stumbles:- in case anyone is still using v0.9 (or possibly earlier) you can access this info from client side like this:

var socket = io.connect();
console.log(socket.socket.transport.name); //log the name of the transport being used.

answer found on google groups https://groups.google.com/forum/#!topic/socket_io/yx_9wJiiAg0

Answer 4

io.connect.managers['connect url/port'].engine.transport

Answer 5

In socket.io 0.7.6

io.sockets.on('connection', function(client) {
    console.log(io.transports[client.id].name);
});

Answer 6

I'm sure you can find it if you dig in the internals of a client object, although without knowing why you need this I have to recommend against this kind of check for 2 reasons:

Firstly, since it isn't in the API the developers have absolutely no responsibility to keep things backward compatible, so any given version might implement/store that information differently, which will only ripple into your own development and cause problems.

Secondly, and more importantly, I suggest you rethink your design, the communication with the server thru socket.io is built to be transparent to the method being used. There should be no difference on either side. That's the purpose of the library, designing an app that behaves otherwise is totally orthogonal to that idea.