Polling as fallback in Flask - Step-by-Step Execution

Concept Flow - Polling as fallback

Client sends request

↓

Server receives request

↓

Server checks for new data

Yes No↓

Send data

↓

Client updates UI

↓

Wait fixed time

↩Back to Client sends request

The client repeatedly asks the server for updates. If new data exists, server sends it; otherwise, it sends an empty response. The client waits then asks again.

Execution Sample

Flask

from flask import Flask, jsonify, request
app = Flask(__name__)

@app.route('/poll')
def poll():
    if new_data_available():
        return jsonify({'data': 'new info'})
    return jsonify({'data': None})

This Flask route checks if new data is available and returns it; otherwise, it returns None as fallback.

Execution Table

Step	Client Request	Server Checks new_data_available()	Server Response	Client Action
1	Sends /poll request	True	Returns {'data': 'new info'}	Updates UI with new info
2	Sends /poll request	False	Returns {'data': None}	No UI update
3	Sends /poll request	False	Returns {'data': None}	No UI update
4	Sends /poll request	True	Returns {'data': 'new info'}	Updates UI with new info
5	Sends /poll request	False	Returns {'data': None}	No UI update
Exit	Stops polling	-	-	Polling ends or continues based on client logic

💡 Polling stops when client decides or page unloads; otherwise, it loops continuously.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	Final
new_data_available()	N/A	True	False	False	True	False	N/A
Server Response	N/A	{'data': 'new info'}	{'data': None}	{'data': None}	{'data': 'new info'}	{'data': None}	N/A
Client UI	Empty	Updated	No change	No change	Updated	No change	Depends on client

Key Moments - 2 Insights

Why does the client keep sending requests even when no new data is available?

Because polling is a fallback method where the client repeatedly asks the server at fixed intervals, even if no new data is ready, as shown in execution_table rows 2 and 3.

What happens on the server when no new data is available?

The server returns a response with data set to None, indicating no update, as seen in execution_table rows 2, 3, and 5.

Visual Quiz - 3 Questions

Look at the execution table, what is the server response at step 4?

A {'data': None}

B {'data': 'new info'}

C No response

D Error message

💡 Hint

Check the 'Server Response' column at step 4 in the execution_table.

At which step does the client update the UI with new data?

A Step 1

B Step 3

C Step 2

D Step 5

💡 Hint

Look at the 'Client Action' column for steps where UI updates happen.

If new_data_available() always returns False, what changes in the execution table?

A Server always returns new info

B Client never sends requests

C Server always returns {'data': None}

D Client updates UI every step

💡 Hint

Refer to the 'Server Checks new_data_available()' and 'Server Response' columns.

Concept Snapshot

Polling as fallback in Flask:
- Client sends repeated requests to server endpoint.
- Server checks for new data each request.
- If new data exists, server sends it; else sends empty response.
- Client updates UI only on new data.
- Polling repeats after fixed wait time as fallback when push not available.

Full Transcript

Polling as fallback means the client keeps asking the server for updates at regular intervals. The server checks if new data is available. If yes, it sends the data back. If no, it sends an empty response. The client updates the user interface only when new data arrives. This cycle repeats until the client stops polling. This method is simple and works when more advanced push methods are not possible.