Broadcasting to rooms in Express - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when broadcasting to a room with no clients?

Consider this Express server using Socket.IO:

io.to('room42').emit('message', 'hello');

What is the behavior when no clients have joined room42?

A No clients receive the message, but no error occurs.

B The server throws an error because the room does not exist.

C The message is queued until a client joins the room.

D The message is sent to all clients connected to the server regardless of room membership.

💡 Hint

Think about how Socket.IO handles empty rooms when emitting.

Socket.IO silently ignores emits to empty rooms. No error is thrown and no clients receive the message.

📝 Syntax

intermediate

Which code correctly broadcasts to all clients except the sender in a specific room?

Given a socket connection, which code sends a message to all clients in room1 except the sender?

A socket.broadcast.to('room1').emit('event', 'data');

B io.to('room1').emit('event', 'data');

C socket.to('room1').emit('event', 'data');

D io.broadcast.to('room1').emit('event', 'data');

💡 Hint

Remember that broadcast excludes the sender.

socket.broadcast.to('room1').emit(...) and socket.to('room1').emit(...) send to all clients in room1 except the sender. io.to('room1') sends to all clients in the room, including the sender if it is in the room.

🔧 Debug

advanced

Why does this broadcast not reach clients in the room?

Look at this code snippet:

socket.on('join', (room) => {
  socket.join(room);
});

socket.on('send', (room, msg) => {
  io.to(room).emit('message', msg);
});

Clients report they never receive the 'message' event. What is the most likely cause?

A The server must use <code>socket.broadcast.to(room)</code> to send messages.

B Clients never actually join the room because <code>socket.join(room)</code> is asynchronous and not awaited.

C The <code>io.to(room).emit</code> call is incorrect; it should be <code>socket.to(room).emit</code>.

D The client-side code is not listening for the 'message' event.

💡 Hint

Consider the asynchronous nature of socket.join.

socket.join(room) returns a promise. If the server emits immediately after calling join without waiting, the socket may not be in the room yet, so clients don't receive the message.

❓ state_output

advanced

How many clients receive the message after these operations?

Assume 3 clients: A, B, and C.

Client A and B join roomX. Client C joins roomY.

Server runs:

io.to('roomX').emit('notify', 'hello');

How many clients receive the 'notify' event?

A 1

B 0

C 3

D 2

💡 Hint

Count clients in roomX.

Only clients A and B are in roomX, so both receive the message. Client C is in a different room.

🧠 Conceptual

expert

What is the effect of using io.in(room).emit() vs io.to(room).emit()?

In Socket.IO, what is the difference between io.in(room).emit('event') and io.to(room).emit('event')?

A <code>io.in(room)</code> sends to all clients except the sender, <code>io.to(room)</code> includes the sender.

B <code>io.in(room)</code> sends only to the room creator, <code>io.to(room)</code> sends to all clients.

C They are aliases and behave identically, sending to all clients in the room.

D <code>io.in(room)</code> sends to clients in nested rooms, <code>io.to(room)</code> sends only to the specified room.

💡 Hint

Check the official Socket.IO documentation for in and to.

io.in(room) and io.to(room) are aliases and behave the same way, sending to all clients in the specified room.