-
Notifications
You must be signed in to change notification settings - Fork 632
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
Namespaces image is misleading #169
Comments
I finally found more info about it under the client api "With multiplexing" portion of the docs and the server api |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey there, I'm a socket.io newb, so forgive me if I'm off here. I believe the image at the top of the namespaces section is a bit misleading. It looks like it is saying the client can can connect to 1 or more namespaces on a single connection but that they are somehow logically separated at some point. This stackoverflow article suggests otherwise.
My understanding, the namespace is in the url of the connection and cannot be changed once the connection is established. If the answer in the article is correct, it should be clarified in the docs. But also, I'd like to understand what the uses of that are? Is it basically just a built-in mechanism to have multiple socket io "servers" in a single process?
The text was updated successfully, but these errors were encountered: