socket.io rooms or namespacing?

by

This is what namespaces and rooms have in common (socket.io v0.9.8 – please note that v1.0 involved a complete rewrite, so things might have changed):

  • Both namespaces (io.of(‘/nsp’)) and rooms (socket.join(‘room’)) are created on the server side
  • Multiple namespaces and multiple rooms share the same (WebSocket) connection
  • The server will transmit messages over the wire only to those clients that connected to / joined a nsp / room, i.e. it’s not just client-side filtering

The differences:

  • namespaces are connected to by the client using io.connect(urlAndNsp) (the client will be added to that namespace only if it already exists on the server)
  • rooms can be joined only on the server side (although creating an API on the server side to enable clients to join is straightforward)
  • namespaces can be authorization protected
  • authorization is not available with rooms, but custom authorization could be added to the aforementioned, easy-to-create API on the server, in case one is bent on using rooms
  • rooms are part of a namespace (defaulting to the ‘global’ namespace)
  • namespaces are always rooted in the global scope

To not confuse the concept with the name (room or namespace), I’ll use compartment to refer to the concept, and the other two names for the implementations of the concept. So if you

  • need per-compartment authorization, namespaces might be the easiest route to take
  • if you want hierarchically layered compartments (2 layers max), use a namespace/room combo
  • if your client-side app consists of different parts that (do not themselves care about compartments but) need to be separated from each other, use namespaces.

An example for the latter would be a large client app where different modules, perhaps developed separately (e.g. third-party), each using socket.io independently, are being used in the same app and want to share a single network connection.

Not having actually benchmarked this, it seems to me if you just need simple compartments in your project to separate and group messages, either one is fine.

Not sure if that answers your question, but the research leading up to this answer at least helped me see clearer.

More Related Contents:

  1. How to share sessions with Socket.IO 1.x and Express 4.x?
  2. Socket.io + Node.js Cross-Origin Request Blocked
  3. WebSockets and Apache proxy: how to configure mod_proxy_wstunnel?
  4. socket.io and session?
  5. nginx as webserver incl. socket.io and node.js / ws:// 400 Bad Request
  6. Get the client’s IP address in socket.io
  7. Socket.IO – how do I get a list of connected sockets/clients?
  8. Which websocket library to use with Node.js? [closed]
  9. What is an example of the simplest possible Socket.io example?
  10. Authenticating socket io connections using JWT
  11. How to reuse redis connection in socket.io?
  12. Use socket.io inside a express routes file
  13. What’s the difference between io.sockets.emit and broadcast?
  14. socket.io and express 4 sessions
  15. How do I get a list of connected sockets/clients with Socket.IO?
  16. Send custom data along with handshakeData in socket.io?
  17. Node.js client for a socket.io server
  18. How to get room’s clients list in socket.io 1.0
  19. Examples in using RedisStore in socket.io
  20. how to list rooms on socket.io nodejs server
  21. Controlling the heartbeat timeout from the client in socket.io
  22. socket.io force a disconnect over XHR-polling
  23. Websocket transport reliability (Socket.io data loss during reconnection)
  24. Separating file server and socket.io logic in node.js
  25. How to resolve a Socket.io 404 (Not Found) error?
  26. Can I access a cookie from Socket.io?
  27. How to use socket.io in express routes?
  28. NPM – Can’t install socket.IO
  29. Socket.io rooms difference between broadcast.to and sockets.in
  30. How to connect two node.js servers with websockets?

Leave a Comment