You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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: