Return individual WebSocket connections about binance-api-node HOT 8 CLOSED

hello guys I need that too.
Thanks lib is awesome!

from binance-api-node.

Related to #13.

Maybe instead of the simple clean callback, we should return an interface that would look like this

{
  socketsBySymbol,
  sockets: cache,
  clean,
}

from binance-api-node.

Is cache in that case just keeping a reference to all sockets from socketsBySymbol?

from binance-api-node.

Cache would be the array of reconnecting websockets as returned by the .map here, socketsBySymbol should be these same sockets indexed by symbol to allow for easier retrieval (no way to tell which socket is for which pair otherwise, unless you keep track of the index yourself, but that's not really ideal)

from binance-api-node.

Just got this problem that the websocket was disconnected and not automatically reconnected. The node.js thread is still blocked but no data is being received, any ideas?

from binance-api-node.

@recidive What version are you using? We recently switch from ws to isomorphic-ws, which could be the issue. Any log output?

from binance-api-node.

I'm running 0.10.29. No logs, unfortunately. No exceptions was thrown. Any tips on how to get some logs? I can try to reproduce the problem again. Thanks!

from binance-api-node.

Hum yeah not sure, try to upgrade to the latest maybe and change this

https://github.com/Ashlar/binance-api-node/blob/master/src/open-websocket.js#L8

from binance-api-node.