options.transports is not honored in node.js

[ichernev]

I'm not sure if this is a feature, but no matter what I pass for transports and 'try multiple transports' if socket.io-client is running in node.js environment it always chooses websockets (or at least that is what the log says).

Here's an example: https://gist.github.com/3039375

Here's the log

[server] setup
   info  - socket.io started
[client] setup
   debug - client authorized
   info  - handshake authorized 15864066021748055096
   debug - setting request GET /socket.io/1/websocket/15864066021748055096
   debug - set heartbeat interval for client 15864066021748055096
   debug - client authorized for 
   debug - websocket writing 1::
[server] connected
[client] connected
[server] emitting msg
   debug - websocket writing 5:::{"name":"msg"}
[client] received 1 msg
[server] got-it event
[server] emitting msg
   debug - websocket writing 5:::{"name":"msg"}
[client] received 2 msg
[server] got-it event
[server] calling disconnect
   info  - booting client
   info  - transport end by forced client disconnection
   debug - websocket writing 0::
   info  - transport end (booted)
   debug - set close timeout for client 15864066021748055096
   debug - cleared close timeout for client 15864066021748055096
   debug - cleared heartbeat interval for client 15864066021748055096
[server] disconnect event
   debug - discarding transport
[client] disconnect event
[server] emitting msg

[jalada]

+1

[ispartan301]

I had the same problem but i got it working by changing the order of params for io.util.interesect() in lib/socket.js. I think this function is not return the right order of transports

[ispartan301]

Also the recent fix in the xhr.js for isXProtocol is necessary as well in order to use xhr-polling

[Wozbo]

I noticed that the socket creation is not overwriting transports, just pushing.either it needs to be migrated to doing merge(this.options, options, 0) or having a special case for transports