Long polling as fallback in Node.js - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is long polling in web communication?

Long polling is a technique where the client sends a request to the server and the server holds the request open until new data is available or a timeout occurs. Then the server responds, and the client immediately sends another request to wait for more data.

beginner

Why use long polling as a fallback method?

Long polling is used as a fallback when real-time communication methods like WebSockets are not supported by the client or network. It simulates real-time updates by repeatedly requesting data from the server.

intermediate

How does long polling differ from regular polling?

Regular polling sends requests at fixed intervals regardless of data availability, which can waste resources. Long polling keeps the request open until data is ready, reducing unnecessary requests and improving efficiency.

intermediate

In Node.js, what is a key consideration when implementing long polling?

You must manage open connections carefully to avoid blocking the event loop. Using asynchronous callbacks and proper timeout handling ensures the server remains responsive while holding requests open.

beginner

What happens on the client side after receiving a response from a long polling request?

The client processes the received data and immediately sends a new long polling request to the server to wait for the next update, maintaining a continuous connection-like experience.

What does long polling do differently compared to regular polling?

A Keeps the request open until data is available or timeout

B Sends requests at fixed intervals regardless of data

C Uses WebSocket protocol for communication

D Closes connection immediately after sending request

Long polling holds the request open until new data is ready or a timeout occurs, unlike regular polling which sends requests at fixed intervals.

Why might long polling be used as a fallback method?

A Because it requires no client requests

B Because it is faster than WebSockets

C Because it uses less server memory than WebSockets

D Because WebSockets are not supported or blocked

Long polling is used when WebSockets are not supported or blocked by the client or network.

In Node.js, what should you avoid when implementing long polling?

A Blocking the event loop with synchronous code

B Using asynchronous callbacks

C Setting timeouts for requests

D Sending multiple requests from the client

Blocking the event loop with synchronous code can make the server unresponsive during long polling.

What does the client do after receiving data from a long polling response?

A Waits for a fixed time before sending another request

B Closes the connection and stops requests

C Sends a new long polling request immediately

D Switches to WebSocket communication

The client immediately sends a new long polling request to keep waiting for updates.

Which of these is NOT a benefit of long polling?

A Reduces unnecessary requests compared to regular polling

B Uses less bandwidth than WebSockets

C Simulates real-time updates without WebSockets

D Works in environments where WebSockets are blocked

Long polling generally uses more bandwidth than WebSockets because it repeatedly opens and closes HTTP connections.

Explain how long polling works as a fallback method for real-time communication.

Think about how the client and server keep talking without WebSockets.

Describe key considerations when implementing long polling in Node.js.

Focus on how Node.js handles many requests at once.

Practice

1. What is the main purpose of using long polling in Node.js applications?

easy

A. To keep a client request open until new data is available

B. To immediately close the connection after sending data

C. To send multiple responses to a single request

D. To replace WebSocket connections entirely

Solution

1. Step 1: Understand long polling behavior

   Long polling keeps the client request open until the server has new data to send.

2. Step 2: Compare options to this behavior

   Only To keep a client request open until new data is available describes this behavior correctly; others describe different or incorrect behaviors.

3. Final Answer:

   To keep a client request open until new data is available -> Option A

4. Quick Check:

   Long polling = open request until data ready [OK]

Hint: Long polling holds request open until data arrives [OK]

Common Mistakes:

• Thinking long polling sends multiple responses per request
• Confusing long polling with WebSocket persistent connection
• Assuming long polling closes connection immediately

2. Which of the following is the correct way to implement a long polling endpoint in Node.js using Express?

easy

A. res.write('data'); // keep connection open without res.end()

B. res.send('data'); res.end();

C. res.json('data'); res.end();

D. res.send('data'); // then wait before closing connection

Solution

1. Step 1: Identify how to keep connection open

   In long polling, the server holds the connection open, so it should not call res.end() immediately.

2. Step 2: Check which option keeps connection open

   res.write('data'); // keep connection open without res.end() uses res.write() without res.end(), which keeps the connection open for long polling.

3. Final Answer:

   res.write('data'); // keep connection open without res.end() -> Option A

4. Quick Check:

   Keep connection open = no res.end() [OK]

Hint: Use res.write() without res.end() to keep connection open [OK]

Common Mistakes:

• Calling res.end() immediately closes connection
• Using res.send() closes connection right away
• Not sending any response causes timeout

3. Consider this Node.js long polling code snippet:

app.get('/poll', (req, res) => {
  setTimeout(() => {
    res.json({ message: 'Update available' });
  }, 5000);
});

What will the client experience when calling this endpoint?

medium

A. The client never receives a response

B. The client receives the update immediately

C. The client waits 5 seconds, then receives the update

D. The client receives multiple updates every 5 seconds

Solution

1. Step 1: Analyze the setTimeout delay

   The server waits 5 seconds before sending the JSON response.

2. Step 2: Understand client wait behavior

   The client request stays open during the 5 seconds, then receives the update once sent.

3. Final Answer:

   The client waits 5 seconds, then receives the update -> Option C

4. Quick Check:

   setTimeout delay = delayed response [OK]

Hint: setTimeout delays response, client waits that time [OK]

Common Mistakes:

• Assuming immediate response despite delay
• Expecting multiple responses from one request
• Thinking client never gets response

4. Given this long polling code snippet, what is the main issue?

app.get('/poll', (req, res) => {
  res.json({ message: 'Update' });
  setTimeout(() => {
    res.json({ message: 'Another update' });
  }, 3000);
});

medium

A. The first res.json() never sends data

B. Calling res.json() twice causes an error

C. setTimeout is not asynchronous

D. The server never responds to the client

Solution

1. Step 1: Understand res.json() behavior

   res.json() sends a response and closes the connection immediately.

2. Step 2: Analyze calling res.json() twice

   Calling res.json() a second time after the connection is closed causes an error.

3. Final Answer:

   Calling res.json() twice causes an error -> Option B

4. Quick Check:

   Multiple res.json() calls = error [OK]

Hint: Only one res.json() per request allowed [OK]

Common Mistakes:

• Thinking setTimeout blocks code
• Assuming multiple res.json() calls send multiple responses
• Ignoring connection close after first response

5. You want to implement long polling as a fallback in a Node.js app that first tries WebSocket. Which approach correctly handles fallback and client reconnection?

hard

A. Use WebSocket and long polling simultaneously, sending duplicate data to client

B. Use WebSocket only; if unavailable, do nothing and drop updates

C. Use long polling only; never try WebSocket to simplify code

D. Use WebSocket; if unavailable, client repeatedly sends GET requests that wait on server until data or timeout, then reconnect

Solution

1. Step 1: Understand fallback strategy

   WebSocket is preferred for real-time, but fallback uses long polling with repeated client requests.

2. Step 2: Identify correct client reconnection method

   The client must send repeated GET requests that wait on server until data or timeout, then reconnect to keep updates flowing.

3. Final Answer:

   Use WebSocket; if unavailable, client repeatedly sends GET requests that wait on server until data or timeout, then reconnect -> Option D

4. Quick Check:

   Fallback = repeated long polling requests [OK]

Hint: Fallback means repeated long polling requests after WebSocket fails [OK]

Common Mistakes:

• Ignoring fallback and dropping updates
• Sending duplicate data by using both methods simultaneously
• Not reconnecting client after long polling timeout