Closed defshift closed 8 years ago
@isotnikov The problem was that the second socketCluster.connect(options)
was returning the previous socket (which is correct) but it wasn't being connected again (it stayed in a disconnected state). This was fixed in v4.3.2.
I'm using socketcluster-client in a angular controller.
At first I try connect to the server and it's connected:
then I try to disconnect on controller destroy event and it's disconnected:
now I try to load controller again and connect to the server again to apply this code:
server sees that connection was initiated, but 'connect' event doesn't work on the client side.