Bird
Raised Fist0
Flaskframework~5 mins

WebSocket events handling in Flask

Choose your learning style10 modes available
Introduction

WebSocket events handling lets your Flask app talk to users instantly. It helps send and receive messages without waiting for page reloads.

You want a chat app where messages appear right away.
You need live updates on a dashboard without refreshing.
You want to notify users instantly about new events.
You build a game that needs real-time player moves.
You want to track live data like stock prices or sensors.
Syntax
Flask
from flask import Flask
from flask_socketio import SocketIO, send, emit

app = Flask(__name__)
socketio = SocketIO(app)

@socketio.on('event_name')
def handle_event(data):
    # code to handle event
    pass

if __name__ == '__main__':
    socketio.run(app)

Use @socketio.on('event_name') to listen for WebSocket events.

Inside the handler, use send() or emit() to reply.

Examples
This listens for a 'message' event and sends back a confirmation.
Flask
@socketio.on('message')
def handle_message(msg):
    send(f'Received: {msg}')
This listens for a 'json' event and emits a 'response' event with data.
Flask
@socketio.on('json')
def handle_json(json_data):
    emit('response', {'data': 'Got your JSON!'})
This runs when a client connects to the WebSocket.
Flask
@socketio.on('connect')
def on_connect():
    print('Client connected')
Sample Program

This Flask app listens for 'message' events from clients. When a message arrives, it prints it on the server and sends a reply back to the client.

Flask
from flask import Flask
from flask_socketio import SocketIO, send

app = Flask(__name__)
socketio = SocketIO(app)

@socketio.on('message')
def handle_message(msg):
    print(f'Received message: {msg}')
    send(f'Server says: {msg}')

if __name__ == '__main__':
    socketio.run(app, debug=True)
OutputSuccess
Important Notes

Remember to run your Flask app with socketio.run(app) instead of app.run().

Use send() for simple messages and emit() for custom events.

WebSocket events let your app be interactive and real-time without page reloads.

Summary

WebSocket events let Flask apps send and receive messages instantly.

Use @socketio.on('event') to handle events and send() or emit() to reply.

This is great for chat, live updates, notifications, and games.

Practice

(1/5)
1. What does the decorator @socketio.on('message') do in a Flask app using WebSocket?
easy
A. It closes the WebSocket connection.
B. It sends a WebSocket message to all connected clients.
C. It listens for incoming WebSocket messages with the event name 'message'.
D. It initializes the Flask app.

Solution

  1. Step 1: Understand the decorator role

    The @socketio.on('message') decorator registers a function to handle incoming WebSocket events named 'message'.
  2. Step 2: Differentiate from other actions

    Sending messages or closing connections are done by other functions, not by this decorator.
  3. Final Answer:

    It listens for incoming WebSocket messages with the event name 'message'. -> Option C
  4. Quick Check:

    Decorator for event handling = C [OK]
Hint: Remember: @socketio.on listens, send() sends [OK]
Common Mistakes:
  • Confusing event handler with sending messages
  • Thinking it closes connections
  • Assuming it initializes the app
2. Which of the following is the correct syntax to send a message back to the client inside a WebSocket event handler in Flask-SocketIO?
easy
A. socketio.send('Hello client!')
B. send('Hello client!')
C. emit('Hello client!')
D. socket.emit('Hello client!')

Solution

  1. Step 1: Identify the correct function call

    In Flask-SocketIO, use the imported send() function inside handlers to reply to the sender client.
  2. Step 2: Check syntax correctness

    A: send('Hello client!') correctly sends to sender. B: socketio.send() sends to all clients. C: emit('Hello client!') uses message as event name without data. D: socket undefined.
  3. Final Answer:

    send('Hello client!') -> Option B
  4. Quick Check:

    Use send() to reply to sender [OK]
Hint: send() replies to sender, socketio.send() to all [OK]
Common Mistakes:
  • Using socketio.send() which sends to all clients
  • Malformed emit() call without data
  • Using undefined socket object
3. Given this Flask-SocketIO event handler code:
@socketio.on('chat')
def handle_chat(msg):
    print('Received:', msg)
    send('Echo: ' + msg)

What will be printed and sent if the client sends the message 'Hi'?
medium
A. Causes a runtime error because send() needs an event name.
B. Prints 'Echo: Hi' and sends 'Received: Hi' back to the client.
C. Prints nothing and sends 'Hi' back to the client.
D. Prints 'Received: Hi' and sends 'Echo: Hi' back to the client.

Solution

  1. Step 1: Analyze the print statement

    The function prints 'Received: ' plus the message, so it prints 'Received: Hi'.
  2. Step 2: Analyze the send() call

    The send() function sends the string 'Echo: ' plus the message back to the client, so it sends 'Echo: Hi'.
  3. Final Answer:

    Prints 'Received: Hi' and sends 'Echo: Hi' back to the client. -> Option D
  4. Quick Check:

    Print then send echo message = D [OK]
Hint: Print shows received, send echoes message [OK]
Common Mistakes:
  • Mixing print output with sent message
  • Assuming send() needs event name
  • Confusing order of print and send
4. Identify the error in this Flask-SocketIO event handler:
@socketio.on('update')
def handle_update():
    data = request.json
    send(data)
medium
A. Using request.json inside WebSocket handler causes an error.
B. Missing event name in @socketio.on decorator.
C. send() cannot send JSON data.
D. Function must have a parameter to receive message data.

Solution

  1. Step 1: Understand request context in WebSocket

    WebSocket handlers do not have HTTP request context, so request.json is not available and causes an error.
  2. Step 2: Check other parts

    The decorator has event name, send() can send JSON, and function can have zero parameters if no message expected.
  3. Final Answer:

    Using request.json inside WebSocket handler causes an error. -> Option A
  4. Quick Check:

    request.json not available in WebSocket handlers [OK]
Hint: Don't use request.json in WebSocket handlers [OK]
Common Mistakes:
  • Assuming HTTP request context exists in WebSocket
  • Thinking send() can't send JSON
  • Believing function must have parameters always
5. You want to broadcast a message to all connected clients except the sender in Flask-SocketIO. Which code snippet correctly does this inside an event handler?
hard
A. emit('broadcast', data, broadcast=true, include_self=false)
B. send(data, broadcast=true, include_self=true)
C. emit('broadcast', data, broadcast=true, include_self=true)
D. send(data, include_self=false)

Solution

  1. Step 1: Understand broadcasting options

    To send to all except sender, use emit() with broadcast=true and include_self=false.
  2. Step 2: Check each option

    B: send(data, broadcast=true, include_self=true) includes sender. C: emit('broadcast', data, broadcast=true, include_self=true) includes sender. D: send(data, include_self=false) lacks broadcast flag. A correctly excludes sender.
  3. Final Answer:

    emit('broadcast', data, broadcast=true, include_self=false) -> Option A
  4. Quick Check:

    Broadcast exclude sender = emit with include_self=false [OK]
Hint: Use emit with broadcast=true and include_self=false [OK]
Common Mistakes:
  • Using send() incorrectly for targeted broadcast
  • Setting include_self=true which includes sender
  • Missing broadcast=true flag
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard