Broadcasting Messages to Multiple Clients

# CHAPTER 9

Broadcasting Messages to Multiple Clients #

1. Introduction #

2. Learning Objectives #

• Define "Broadcasting" in the context of WebSockets.

• Understand how a server maintains a list of connected clients.

• Explain the concept of "Rooms" or "Channels".

• Trace the flow of a message from one sender to multiple receivers.

3. Beginner-Friendly Explanation #

• Point-to-Point (Echo): A student hands the teacher a note. The teacher reads it and hands it right back to that specific student. Nobody else sees it.

• Broadcasting: A student hands the teacher a note. The teacher stands up and reads the note loudly so the entire classroom can hear it.

In WebSockets, every time a user connects, the server adds them to a "classroom" (an array or list of connections). When a message arrives, the server loops through that list and sends the message to everyone.

4. Real-World Examples #

• Global Broadcast: A server-wide notification in an online game ("Server will restart in 5 minutes"). It goes to every single connected user.

• Room Broadcast: A WhatsApp group chat. Only the 10 people inside the "Family Group" room receive the broadcast, not the millions of other users on WhatsApp.

5. Architectural Step-by-Step #

Step 1: Server starts up and creates an empty list called Clients = []. Step 2: User A connects. Server adds User A to the list: Clients = [A]. Step 3: User B connects. Server adds User B: Clients = [A, B]. Step 4: User A sends a message to the server: "Hello everyone!". Step 5: Server receives the message, runs a foreach loop over Clients, and calls send("Hello everyone!") on both A and B.

6. The "Echo vs Broadcast" Problem #

7. Conceptual Server Logic (Pseudocode) #

function onMessage(senderConnection, incomingMessage) {
    
    // Loop through every person currently connected
    foreach (client in globalClientsList) {
        
        // Don't send it back to the person who wrote it!
        if (client !== senderConnection) {
            client.send(incomingMessage);
        }
    }
}

8. JSON Structure for Rooms #

{
  "action": "send_to_room",
  "room": "gaming_lounge",
  "message": "Who wants to play?"
}

The server then checks its memory, finds the gaming_lounge array, and only loops through those specific clients.

9. PHP Broadcasting Preview (Ratchet) #

<?php
public function onMessage(ConnectionInterface $from, $msg) {
    foreach ($this->clients as $client) {
        if ($from !== $client) {
            // The sender is not the receiver, send to each client connected
            $client->send($msg);
        }
    }
}

10. Best Practices #

• Manage Disconnections: If User B loses internet, the server must remove User B from the Clients array immediately. If it tries to broadcast to a dead connection, it will throw an error and potentially crash the loop.

• Use JSON for routing: Never try to parse plain strings on the server to determine who gets a message. Always wrap messages in JSON objects with an explicit type or action property.

11. Common Mistakes #

• Forgetting to exclude the sender: Resulting in duplicate messages showing up on the sender's screen.

• Blocking the Event Loop: If a server has 10,000 clients, a single broadcast requires looping 10,000 times. If the broadcast logic takes too long, it will freeze the server. Efficient memory management is key.

12. Mini Exercises #

1. 1. Sketch a diagram on a piece of paper: Draw one Server in the middle, and 3 Clients (A, B, C) connected to it. Draw an arrow from A to Server labeled "Message". Then draw arrows from Server to B and Server to C. You have just mapped out a Broadcast!

13. Coding Challenges #

14. MCQs with Answers #

15. Interview Questions #

• Q: How does a WebSocket server keep track of who is currently online?

• Q: Explain how you would architect a "Private Message" feature (Client A to Client B) instead of a global broadcast.

16. FAQs #

17. Summary #

18. Next Chapter Recommendation #