Problem with multiple sockets on reconnect

[Ulrik Sorber]

Hi all,

This problem seems to have persisted for a long time.
And I have not been able to find a solution though there are a lot of creative suggestions to remedy this problem, from maintaining the the socket list via. socket.id or by keeping track of the time stamps on each request.
Anyhow, since this is a known and pretty annoying bug. will it be fixed?

Or is there a reasonable workaround that can be applied?

/Ulrik

[mark]

There are many other issues with reconnects, and after applying more and more bugfixes to socket.io 0.9.x (you can see some of the recent pull requests) I came to the conclusion it would be easier to just use engine.io.

[Ulrik Sorber]

Ill have to check engine.io out. This reconnection issue is a complete show stopper.

Thanks for the tip.

/Ulrik

--
You received this message because you are subscribed to the Google Groups "Socket.IO" group.
To unsubscribe from this group and stop receiving emails from it, send an email to socket_io+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Filipe]

What is the multiple socket problem? Curious

[Ulrik Sorber]

What is the multiple socket problem? Curious

The problem occurs when you kill the server and restart it again within seconds.

When this happens, socket.io often reconnects multiple times, before the client side disconnect event is fired, which prevents me from handling and correcting the problem my self.

After this, all messages are multiplied.

Any clues?

/Ulrik

[Ulrik Sorber]

FUI

After having updated chrome to Version 30.0.1599.10 dev-m i don't see any problems with multiple connections on reconnects anymore.

I can't tell if this is related to the latest chrome changes.
I also changed the emitters functions to using references instead of anonymous functions.

All in all i can't tell why the problem has suddenly disapeared :-/ but it seems to work correctly

/Ulrik