How should you architect a Flask app to use WebSocket for real-time updates and fallback to polling for clients without WebSocket support?

hard📝 Application Q8 of 15

Flask - WebSocket and Real-Time

AUse polling endpoints only and ignore WebSocket support

BImplement WebSocket endpoints for real-time, and provide separate HTTP polling endpoints as fallback

CUse WebSocket endpoints and force all clients to upgrade to WebSocket

DCombine WebSocket and polling in the same endpoint using POST requests

Step-by-Step Solution

Solution:

Step 1: Understand dual support
WebSocket provides real-time updates; polling is fallback for unsupported clients.
Step 2: Separate endpoints
Maintain WebSocket endpoints for real-time and HTTP polling endpoints for fallback.
Final Answer:
Implement WebSocket endpoints for real-time, and provide separate HTTP polling endpoints as fallback -> Option B
Quick Check:
Separate endpoints ensure compatibility and maintainability [OK]

Quick Trick: Use separate endpoints for WebSocket and polling [OK]

Common Mistakes:

MISTAKES

Master "WebSocket and Real-Time" in Flask

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Flask Quizzes