WebSocket events handling in Flask - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output when a client connects?

Consider this Flask-SocketIO server code snippet. What message will the server send to the client immediately after connection?

Flask

from flask_socketio import SocketIO, emit

socketio = SocketIO()

@socketio.on('connect')
def handle_connect():
    emit('welcome', {'msg': 'Hello, client!'})

A The client receives no message until it sends a message first

B The client receives an event 'connect' with data {'msg': 'Hello, client!'}

C The client receives an event 'welcome' with data {'msg': 'Hello, client!'}

D The server raises an error because emit is not allowed in connect event

💡 Hint

Remember that emit sends events to the client. The event name is the first argument.

In Flask-SocketIO, emitting inside the connect event sends the specified event to the client immediately after connection. Here, the event name is 'welcome' with the given data.

❓ state_output

intermediate

What is the value of 'count' after three 'increment' events?

Given this Flask-SocketIO server code, what will be the value of count after the client sends the 'increment' event three times?

Flask

from flask_socketio import SocketIO, emit

socketio = SocketIO()
count = 0

@socketio.on('increment')
def handle_increment():
    global count
    count += 1
    emit('count_updated', {'count': count})

A 1

B 3

C 0

D Raises UnboundLocalError

💡 Hint

Check how the count variable is updated and the use of global.

The count variable is declared global and incremented by 1 each time the 'increment' event is handled. After three events, count becomes 3.

📝 Syntax

advanced

Which option causes a SyntaxError in Flask-SocketIO event handler?

Identify which code snippet will cause a syntax error when defining a Flask-SocketIO event handler.

A

@socketio.on('message')
def handle_message()
    print('Message received')

B

@socketio.on('message')
def handle_message():
    print('Message received')

C

@socketio.on('message')
def handle_message():
    emit('response', {'data': 'ok'})

D

@socketio.on('message')
async def handle_message():
    await some_async_func()

💡 Hint

Look for missing punctuation or incorrect function definitions.

Option A is missing a colon at the end of the function definition line, causing a SyntaxError.

🔧 Debug

advanced

Why does the server not respond to 'chat' events?

Given this Flask-SocketIO server code, the client sends 'chat' events but receives no response. What is the likely cause?

Flask

from flask_socketio import SocketIO, emit

socketio = SocketIO()

@socketio.on('message')
def handle_message(data):
    emit('response', {'msg': data['msg']})

A The function handle_message lacks the global keyword for data

B The emit call is missing the broadcast=True argument

C The server must use @socketio.event decorator instead of @socketio.on

D The event handler listens for 'message' but client sends 'chat', so no handler is triggered

💡 Hint

Check if the event names match between client and server.

The server listens for 'message' events but the client sends 'chat' events. Since event names differ, the handler is never called.

🧠 Conceptual

expert

What happens if you emit an event outside a SocketIO event context?

In Flask-SocketIO, what is the behavior when you call emit('update', data) outside of any event handler or request context?

A Emit raises a RuntimeError because there is no active SocketIO context

B Emit sends the event to all connected clients automatically

C Emit queues the event and sends it when a client connects

D Emit silently does nothing without error

💡 Hint

Think about how Flask-SocketIO manages context for emitting events.

Emitting events requires an active SocketIO context (inside an event handler or request). Outside this, emit raises a RuntimeError.