Skip to content
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

Open
rhythmize opened this issue Jun 13, 2018 · 5 comments
Open

Issues while using socketIO-client library #189

rhythmize opened this issue Jun 13, 2018 · 5 comments

Comments

@rhythmize
Copy link

rhythmize commented Jun 13, 2018

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:

  1. 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)
  2. 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).
  3. 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.

Regards
Rhythm

@rhythmize
Copy link
Author

Has anyone else faced these issues or am I missing something here?

@xxxenobyte
Copy link

xxxenobyte commented Jul 3, 2018

++
the same problem as in the first case

@rhythmize
Copy link
Author

Have you found a fix?

@xxxenobyte
Copy link

@Code-Player no =(

@rake1191
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants