Room and namespace concepts in Node.js - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when a client joins a room in a namespace?

Consider a Socket.IO server with namespaces and rooms. When a client connects to a namespace and joins a room, what is the effect on message delivery?

Node.js

const io = require('socket.io')(3000);
const chat = io.of('/chat');
chat.on('connection', socket => {
  socket.join('room1');
  chat.to('room1').emit('message', 'Hello Room 1');
});

A Only clients connected to '/chat' namespace and joined 'room1' receive the 'message' event.

B All clients connected to the server receive the 'message' event regardless of namespace or room.

C Only clients connected to the default namespace receive the 'message' event.

D Clients in any namespace joined to 'room1' receive the 'message' event.

💡 Hint

Think about how namespaces isolate communication and rooms group clients within a namespace.

Namespaces separate clients logically. Rooms are subsets within a namespace. Emitting to a room in a namespace sends only to clients in that room and namespace.

📝 Syntax

intermediate

Which code correctly creates a namespace and joins a client to a room?

Identify the correct code snippet that creates a namespace '/news' and joins a client socket to a room 'updates'.

A

const news = io.of('/news');
news.on('connection', socket => {
  socket.join('updates');
});

B

const news = io.of('/news');
io.on('connection', socket => {
  socket.join('updates');
});

C

const news = io.of('/news');
news.on('connect', socket => {
  socket.join('updates');
});

D

const news = io.of('/news');
news.on('connection', socket => {
  news.join('updates');
});

💡 Hint

Remember the event name for new connections and how to join a room on the socket object.

The 'connection' event is emitted on the namespace when a client connects. The socket object has the 'join' method to join rooms. Option A uses both correctly.

🔧 Debug

advanced

Why does emitting to a room not reach clients in another namespace?

Given this code, clients in '/chat' namespace joined to 'room1' do not receive messages emitted to 'room1' from '/news' namespace. Why?

const chat = io.of('/chat');
const news = io.of('/news');

chat.on('connection', socket => {
  socket.join('room1');
});

news.on('connection', socket => {
  news.to('room1').emit('message', 'Hello Room1');
});

A Clients must join rooms on both namespaces to receive messages.

B The 'to' method only works on the default namespace, not custom namespaces.

C Rooms are scoped to namespaces, so 'room1' in '/news' is different from 'room1' in '/chat'.

D The emit call is missing the socket object, so no clients receive the message.

💡 Hint

Think about how namespaces and rooms relate in Socket.IO.

Rooms exist within namespaces. The same room name in different namespaces refers to different groups. Emitting to 'room1' in '/news' does not reach clients in '/chat'.

❓ state_output

advanced

How many clients receive the message after joining multiple rooms?

Consider a client socket that joins two rooms 'roomA' and 'roomB' in the same namespace. If the server emits a message to both rooms separately, how many times does the client receive the message?

socket.join('roomA');
socket.join('roomB');

namespace.to('roomA').emit('msg', 'Hello A');
namespace.to('roomB').emit('msg', 'Hello B');

A The client receives one message with combined content from both rooms.

B The client receives two separate messages: one from 'roomA' and one from 'roomB'.

C The client receives only one message because rooms are merged.

D The client receives no messages because it cannot join multiple rooms.

💡 Hint

Think about how emitting to rooms works and how clients receive events.

Joining multiple rooms means the client is in both groups. Emitting separately to each room sends separate events. The client receives both messages independently.

🧠 Conceptual

expert

What is the main benefit of using namespaces with rooms in Socket.IO?

Why would a developer use namespaces combined with rooms instead of just rooms alone?

A Using namespaces disables the need for rooms because they serve the same purpose.

B Namespaces automatically broadcast messages to all clients, rooms restrict messages to one client only.

C Rooms are global across all namespaces, namespaces limit clients to one room only.

D Namespaces provide logical separation of communication channels, while rooms allow grouping within those channels for targeted messaging.

💡 Hint

Consider how namespaces and rooms organize clients differently.

Namespaces separate clients into different communication channels. Rooms group clients within those channels. This layered approach allows fine control over message delivery.