'connect' event not fired, but connected is true.

[vicary]

I am using socket.io-client 1.1.0 from CDN, and connects to my server which is also 1.1.0.

My page is under heavy load on startup, which takes care of all the initialization stuffs.

I found that the 'connect' event at client side is fired around 20% of the time, but checking socket.connected after page load is always true.

I suspect that the connect event is fired before it binds to my event handlers.

I think when a new event handler binds to the connect event, and the socket is currently connected, that handler should be triggered immediately.

[nkzawa]

An event can be fired multiple times, so we can't support that behavior IMO.

Usually, you don't have to listen connect event, since sent data are buffered until the connection is established. You can just listen and emit any events without waiting the connect event.
If you have to wait the event anyway, there is autoConnect option which you can control when to connect.

[vicary]

It's like the listening event of http, just fire it once at the time of binding.

[vicary]

My app uses a hash key from a cookie in another domain to do authorization, which I was binding a custom authorize event on connect. I tried with the new io.use authorize way, but it actually generates #776...

[nkzawa]

Actually connect event can fire multiple times when successful reconnections.

[vicary]

Just want to make sure if rooms joined at server-side will survive reconnections, coz sid is different.

tl;dr

In my app, an authenticated socket will be put into serveral internal broadcast rooms at server-side, currently I have no way to make sure the socket is still in those rooms after reconnection at client side (docs didn't mention it). I just fire the authentication event every time it connects/reconnects.

[nkzawa]

You have to join rooms again on reconnection, because, as you described already, sid and socket are different on server side.

[vicary]

I will do on my code on load for if (socket.connected). If this is not gonna be supported, I'm closing this.