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 add unnecessary complexity? #3

Open
madari opened this issue Mar 25, 2011 · 1 comment
Open

Namespaces add unnecessary complexity? #3

madari opened this issue Mar 25, 2011 · 1 comment

Comments

@madari
Copy link

madari commented Mar 25, 2011

I think it would be a better idea to keep the feature set as simple as possible
and focus on the quality instead. Let other people build more complex application-level stuff (e.g. namespaces) on top of the bare sockets.

Are you sure you want to implement "namespaces" in Socket.IO?

@3rd-Eden
Copy link

There are a few different usecases for namespaces. First the most common request is channels. People only want to broadcast or message a small section of the connected users. By implementing namespaces this will become possible.

There are already a few modules written ontop of Socket.IO, they all create there own connection with the server. So you have want to run Socket.IO normally + an abstraction you would have to create 2 persistent connections with the server and this is something we are trying to prevent.

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

2 participants