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

Protocol discussion: CLOSE vs. DISCONNECT #167

Open
evgeny-pasynkov opened this issue Oct 2, 2014 · 0 comments
Open

Protocol discussion: CLOSE vs. DISCONNECT #167

evgeny-pasynkov opened this issue Oct 2, 2014 · 0 comments

Comments

@evgeny-pasynkov
Copy link

Hi,

Reversing socket.io 1.0 protocol, I see 2 packet types:

  1. CLOSE connection
  2. MESSAGE:DISCONNECT for namespace

Occasionally (I still investigating this, but it is hardly reproducible) clients sends MESSAGE:DISCONNECT for root namespace, and then tries to connect it again. But server closes connection in this case, and further it fails with log:

ERROR - tio.transport.PollingTransport - 3ae6e5a0-1f87-4488-a80c-e8571f9c1d18 is not registered. Closing connection

and then more subsequent errors.

Maybe it is reasonable to wait for a while before closing connection on root namespace disconnect?

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