WebSockets for real-time communication in Computer Networks - Time & Space Complexity

Time Complexity: WebSockets for real-time communication

O(n)

Understanding Time Complexity

When using WebSockets for real-time communication, it is important to understand how the time taken to send and receive messages changes as more messages or users are involved.

We want to know how the system handles increasing communication load efficiently.

Scenario Under Consideration

Analyze the time complexity of this simplified WebSocket server handling messages.

// Pseudocode for WebSocket message broadcast
function onMessageReceived(message) {
  for (let client of connectedClients) {
    client.send(message);
  }
}

This code sends a received message to all connected clients, broadcasting it in real-time.

Identify Repeating Operations

Look at what repeats when a message arrives.

• Primary operation: Sending the message to each connected client.
• How many times: Once for every client connected to the server.

How Execution Grows With Input

As the number of clients grows, the number of send operations grows too.

Input Size (n)	Approx. Operations
10 clients	10 sends
100 clients	100 sends
1000 clients	1000 sends

Pattern observation: The work grows directly with the number of clients; doubling clients doubles the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to broadcast a message grows linearly with the number of connected clients.

Common Mistake

[X] Wrong: "Sending a message to all clients takes the same time no matter how many clients there are."

[OK] Correct: Each client needs its own send operation, so more clients mean more work and more time.

Interview Connect

Understanding how message broadcasting scales helps you design systems that handle many users smoothly, a key skill in real-time communication roles.

Self-Check

What if the server only sent messages to a fixed number of clients instead of all? How would the time complexity change?

Practice

1. What is the main advantage of using WebSockets for communication between a client and a server?

easy

A. They only allow one-way communication from server to client.

B. They allow real-time, two-way communication without repeatedly opening new connections.

C. They require a new connection for every message sent.

D. They work only for static web pages without interaction.

Solution

1. Step 1: Understand WebSocket communication

   WebSockets keep a single connection open for continuous two-way data exchange.

2. Step 2: Compare with other methods

   Unlike HTTP requests, WebSockets avoid opening new connections for each message.

3. Final Answer:

   They allow real-time, two-way communication without repeatedly opening new connections. -> Option B

4. Quick Check:

   Two-way real-time communication = They allow real-time, two-way communication without repeatedly opening new connections. [OK]

Hint: WebSockets keep one open connection for instant two-way chat [OK]

Common Mistakes:

• Thinking WebSockets only send data one way
• Confusing WebSockets with HTTP polling
• Assuming new connection per message

2. Which of the following is the correct way to create a WebSocket connection in JavaScript?

easy

A. const socket = new WebSocket('http://example.com');

B. const socket = WebSocket.connect('ws://example.com');

C. const socket = WebSocket('https://example.com');

D. const socket = new WebSocket('ws://example.com');

Solution

1. Step 1: Identify correct WebSocket URL scheme

   WebSocket URLs start with ws:// or wss:// for secure connections.

2. Step 2: Check JavaScript syntax

   The correct syntax uses new WebSocket(url) with the ws:// scheme.

3. Final Answer:

   const socket = new WebSocket('ws://example.com'); -> Option D

4. Quick Check:

   WebSocket URL starts with ws:// = const socket = new WebSocket('ws://example.com'); [OK]

Hint: WebSocket URLs start with ws:// or wss:// [OK]

Common Mistakes:

• Using http:// or https:// instead of ws://
• Calling WebSocket without new keyword
• Using incorrect method like WebSocket.connect

3. Consider this JavaScript code snippet using WebSocket:

const socket = new WebSocket('ws://example.com');
socket.onopen = () => socket.send('Hello');
socket.onmessage = (event) => console.log(event.data);

What will happen when the connection opens?

medium

A. The message 'Hello' is sent to the server, and incoming messages are logged.

B. The message 'Hello' is logged to the console, but nothing is sent.

C. An error occurs because send cannot be called on open event.

D. Nothing happens until the server sends a message first.

Solution

1. Step 1: Analyze the onopen event handler

   When the WebSocket connection opens, it sends the string 'Hello' to the server.

2. Step 2: Analyze the onmessage event handler

   Any message received from the server is logged to the console.

3. Final Answer:

   The message 'Hello' is sent to the server, and incoming messages are logged. -> Option A

4. Quick Check:

   Send on open + log messages = The message 'Hello' is sent to the server, and incoming messages are logged. [OK]

Hint: onopen sends, onmessage logs incoming data [OK]

Common Mistakes:

• Thinking send cannot be called on open
• Confusing logging sent message vs received message
• Assuming no action until server sends first

4. A developer wrote this code to open a WebSocket and send a message:

const socket = new WebSocket('ws://example.com');
socket.send('Hi');

What is the problem with this code?

medium

A. The send method is called before the connection is open.

B. The URL should start with https:// instead of ws://.

C. The WebSocket constructor requires a callback function.

D. The message 'Hi' must be sent as an object, not a string.

Solution

1. Step 1: Check WebSocket connection timing

   The send method must be called only after the connection is open.

2. Step 2: Identify error in code

   Calling send immediately after creating the socket tries to send before connection is ready, causing an error.

3. Final Answer:

   The send method is called before the connection is open. -> Option A

4. Quick Check:

   send before open causes error = The send method is called before the connection is open. [OK]

Hint: Wait for onopen event before sending messages [OK]

Common Mistakes:

• Using https:// instead of ws:// for WebSocket URL
• Expecting constructor to take a callback
• Sending non-string data without serialization

5. You want to build a live sports score dashboard using WebSockets. Which approach best ensures the dashboard updates instantly and efficiently?

hard

A. Open a new WebSocket connection for each score update.

B. Use HTTP polling every 5 seconds to fetch the latest scores.

C. Open a WebSocket connection once and update scores as messages arrive.

D. Send all scores once when the page loads and never update.

Solution

1. Step 1: Understand real-time update needs

   A live dashboard needs instant updates without delay or repeated connection overhead.

2. Step 2: Evaluate options for efficiency

   Opening one WebSocket connection and receiving updates as messages is efficient and real-time.

3. Step 3: Eliminate less efficient methods

   Polling causes delay and overhead; opening many connections wastes resources; sending once misses updates.

4. Final Answer:

   Open a WebSocket connection once and update scores as messages arrive. -> Option C

5. Quick Check:

   Single open connection + live updates = Open a WebSocket connection once and update scores as messages arrive. [OK]

Hint: One open WebSocket connection handles all live updates efficiently [OK]

Common Mistakes:

• Using polling instead of WebSocket for real-time
• Opening multiple connections unnecessarily
• Not updating after initial data load