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

Namespaces image is misleading #169

Open
bzuillsmith opened this issue Sep 4, 2020 · 1 comment
Open

Namespaces image is misleading #169

bzuillsmith opened this issue Sep 4, 2020 · 1 comment

Comments

@bzuillsmith
Copy link

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?

@bzuillsmith
Copy link
Author

I finally found more info about it under the client api "With multiplexing" portion of the docs and the server api of documentation. Between all those sources, it's starting to make sense. I think it would be best to add some examples of client and server code in the namespaces doc. A little duplication from the other docs wouldn't probably be fine. It would make it easier to find and understand.

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

1 participant