https://ai-blog.noorshomelab.dev/tags/agnostic/Recent content in Agnostic on AI VOIDHugoenWed, 20 Aug 2025 00:00:00 +0000https://ai-blog.noorshomelab.dev/chat-guide/chapter-5-connection-manager/Wed, 20 Aug 2025 00:00:00 +0000https://ai-blog.noorshomelab.dev/chat-guide/chapter-5-connection-manager/<p>Our current WebSocket endpoint only echoes messages back to the sender. A real chat application needs to handle multiple users, allowing them to join, leave, and send messages that are broadcast to all other connected users (or users in a specific room). This chapter introduces a WebSocket connection manager to address this.</p> <h3 id="purpose-of-this-chapter">Purpose of this Chapter</h3> <p>By the end of this chapter, you will:</p> <ul> <li>Understand the need for a connection manager in a real-time application.</li> <li>Implement a <code>ConnectionManager</code> class to store and manage active WebSocket connections.</li> <li>Modify the WebSocket endpoint to use the manager for connecting, disconnecting, and broadcasting messages.</li> <li>Test broadcasting functionality with multiple client connections.</li> </ul> <h3 id="concepts-explained-connection-management">Concepts Explained: Connection Management</h3> <p>When a client connects via WebSocket, the <code>WebSocket</code> object represents that specific connection. To send a message to all active clients, or a subset of them, our server needs a way to keep track of these individual <code>WebSocket</code> objects. A <code>ConnectionManager</code> class typically serves this purpose.</p>