Server-Sent Events alternative in Flask - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Flask class.

Flask

from flask import [1]

Drag options to blanks, or click blank then click option'

AFlask

Brender_template

CSession

DRequest

Attempts:

3 left

💡 Hint

Common Mistakes

Importing Request instead of Flask

Using lowercase flask instead of Flask

The Flask class is imported from the flask module to create the app.

2fill in blank

medium

Complete the code to create a Flask app instance.

Flask

app = [1](__name__)

Drag options to blanks, or click blank then click option'

Asession

Brequest

CFlask

Drender_template

Attempts:

3 left

💡 Hint

Common Mistakes

Using request or session instead of Flask

Forgetting to pass __name__

Creating the Flask app requires calling Flask with __name__.

3fill in blank

hard

Fix the error in the route decorator to define a streaming endpoint.

Flask

@app.route('/stream', [1]=['GET'])

Drag options to blanks, or click blank then click option'

Amethod

Bmethods

Croute

Dendpoint

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'method' instead of 'methods'

Using 'route' or 'endpoint' which are incorrect here

The correct keyword argument to specify HTTP methods is 'methods'.

4fill in blank

hard

Fill both blanks to create a generator function that yields messages for streaming.

Flask

def event_stream():
    while True:
        yield [1] + '\n\n'
        time.sleep([2])

Drag options to blanks, or click blank then click option'

A'data: Hello World!'

B'event: message'

C1

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Yielding without 'data:' prefix

Using too long or zero sleep time

The generator yields a string starting with 'data:' followed by two newlines, then sleeps 1 second.

5fill in blank

hard

Fill all three blanks to return a streaming response with correct mimetype.

Flask

from flask import Response

@app.route('/stream')
def stream():
    return Response([1](), mimetype=[2])

# Use [3] mimetype for Server-Sent Events

Drag options to blanks, or click blank then click option'

Aevent_stream

B'text/event-stream'

C'application/json'

D'text/plain'

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong mimetype like 'application/json' or 'text/plain'

Calling the generator without parentheses

The Response uses the event_stream generator and 'text/event-stream' mimetype for SSE.

Practice

1. What is a common alternative to Server-Sent Events (SSE) for real-time communication in Flask applications?

easy

A. Static HTML pages

B. Regular HTTP GET requests

C. WebSockets using Flask-SocketIO

D. Email notifications

Solution

1. Step 1: Understand SSE purpose

   Server-Sent Events send updates one-way from server to browser for real-time data.

2. Step 2: Identify alternative for two-way communication

   WebSockets allow two-way real-time communication and Flask-SocketIO simplifies their use in Flask.

3. Final Answer:

   WebSockets using Flask-SocketIO -> Option C

4. Quick Check:

   Real-time two-way communication = WebSockets [OK]

Hint: WebSockets enable two-way real-time updates, unlike SSE [OK]

Common Mistakes:

• Confusing SSE with regular HTTP requests
• Thinking static pages can update in real-time
• Assuming email is real-time communication

2. Which of the following is the correct way to import Flask-SocketIO in a Flask app?

easy

A. from flask_socketio import SocketIO

B. import flask_socketio.SocketIO

C. from flask import SocketIO

D. import SocketIO from flask_socketio

Solution

1. Step 1: Recall correct import syntax in Python

   Python uses 'from module import class' to import specific classes.

2. Step 2: Match Flask-SocketIO import pattern

   The correct import is 'from flask_socketio import SocketIO' to get the SocketIO class.

3. Final Answer:

   from flask_socketio import SocketIO -> Option A

4. Quick Check:

   Correct Python import syntax = from flask_socketio import SocketIO [OK]

Hint: Use 'from module import class' for specific imports in Python [OK]

Common Mistakes:

• Using JavaScript import syntax in Python
• Importing SocketIO from flask instead of flask_socketio
• Incorrect module or class names

3. Given this Flask-SocketIO code snippet, what will the client receive when the server emits 'message' event?

from flask_socketio import SocketIO, emit

socketio = SocketIO(app)

@socketio.on('connect')
def handle_connect():
    emit('message', {'data': 'Welcome!'})

medium

A. No message is sent on connect

B. A plain text message 'Welcome!'

C. An error because emit needs a string message

D. A JSON object with {'data': 'Welcome!'}

Solution

1. Step 1: Understand the emit function usage

   emit sends an event with a dictionary payload as JSON to the client.

2. Step 2: Analyze the event and data sent on connect

   On 'connect', the server emits 'message' event with {'data': 'Welcome!'} dictionary.

3. Final Answer:

   A JSON object with {'data': 'Welcome!'} -> Option D

4. Quick Check:

   emit sends JSON data = A JSON object with {'data': 'Welcome!'} [OK]

Hint: emit sends JSON-like dict, not plain text [OK]

Common Mistakes:

• Thinking emit sends plain text only
• Assuming emit requires string, not dict
• Believing no message is sent on connect

4. Identify the error in this Flask-SocketIO server code:

from flask_socketio import SocketIO

socketio = SocketIO(app)

@socketio.on('message')
def handle_message(data):
    print('Received:', data)

socketio.run(app)

medium

A. Function handle_message missing return statement

B. Missing import of Flask app

C. No event handler for 'connect'

D. Using socketio.run instead of app.run

Solution

1. Step 1: Check imports and app definition

   The code uses 'app' but does not import or define it anywhere.

2. Step 2: Confirm socketio.run usage

   socketio.run(app) is correct to run the app with SocketIO support.

3. Final Answer:

   Missing import of Flask app -> Option B

4. Quick Check:

   Undefined app variable = Missing import of Flask app [OK]

Hint: Always define or import Flask app before using it [OK]

Common Mistakes:

• Confusing socketio.run with app.run
• Thinking event handlers must return values
• Assuming 'connect' event handler is mandatory

5. You want to replace Server-Sent Events with Flask-SocketIO for a chat app. Which approach correctly handles broadcasting a message to all connected clients?

hard

A. Use socketio.emit('chat', message, broadcast=True) inside an event handler

B. Use emit('chat', message) without broadcast inside the handler

C. Use socketio.send(message) without event name

D. Use app.run() with broadcast=True parameter

Solution

1. Step 1: Understand broadcasting in Flask-SocketIO

   To send a message to all clients, use socketio.emit with broadcast=True.

2. Step 2: Evaluate options for broadcasting

   Use socketio.emit('chat', message, broadcast=True) inside an event handler correctly uses socketio.emit with event name and broadcast flag.

3. Final Answer:

   Use socketio.emit('chat', message, broadcast=True) inside an event handler -> Option A

4. Quick Check:

   Broadcast all clients = socketio.emit with broadcast=True [OK]

Hint: Broadcast with socketio.emit and broadcast=True [OK]

Common Mistakes:

• Omitting broadcast=True to send to all clients
• Using emit without socketio object for broadcast
• Trying to broadcast via app.run parameters