Hi,
I was testing this library to be used in project involving socket connections to a socket server. Following are some of the issues I faced:
socket client is not continuously listening for events triggered by the server (I have to make a blocking call manager.wait()). Thus handlers are not executed as soon as server triggers a custom event. (This seems a big issue because socket connections are meant to be realtime)
On connecting to custom namespace /sub of the server (using manager.define(Namespace, '/sub')), socket.emit("event") works even after the client is disconnected from that namespace (either by client or server).
Once disconnected, if client again connects to server namespace (using manager.define(Namespace, '/sub')), it pics up the same connection-id as before whereas once disconnected, client should pick up new connection-id.
I don't know if someone else faced these issues, but please suggest if I got something wrong in using the library or above mentioned points are features or actually issues.
Please respond soon. I need this library to embed in a Flask application.
Hi, I was testing this library to be used in project involving socket connections to a socket server. Following are some of the issues I faced:
manager.wait()
). Thus handlers are not executed as soon as server triggers a custom event. (This seems a big issue because socket connections are meant to be realtime)/sub
of the server (using manager.define(Namespace, '/sub')
),socket.emit("event")
works even after the client is disconnected from that namespace (either by client or server).using manager.define(Namespace, '/sub')
), it pics up the same connection-id as before whereas once disconnected, client should pick up new connection-id.I don't know if someone else faced these issues, but please suggest if I got something wrong in using the library or above mentioned points are features or actually issues.
Please respond soon. I need this library to embed in a Flask application.
Regards Rhythm