-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues while using socketIO-client library #189
Comments
Has anyone else faced these issues or am I missing something here? |
++ |
Have you found a fix? |
@Code-Player no =( |
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: