Bird
0
0

Why does a WebSocket connection on a Raspberry Pi remain open after the initial handshake, unlike HTTP?

hard🧠 Conceptual Q10 of 15
Raspberry Pi - Web Server and API
Why does a WebSocket connection on a Raspberry Pi remain open after the initial handshake, unlike HTTP?
ABecause WebSocket uses a persistent TCP connection for continuous data exchange
BBecause WebSocket closes immediately after sending data
CBecause WebSocket uses UDP which is connectionless
DBecause WebSocket requires manual reconnection after each message
Step-by-Step Solution
Solution:
  1. Step 1: Understand WebSocket connection nature

    WebSocket upgrades HTTP to a persistent TCP connection for ongoing communication.
  2. Step 2: Compare with HTTP behavior

    HTTP opens and closes connection per request; WebSocket keeps it open for live updates.
  3. Final Answer:

    Because WebSocket uses a persistent TCP connection for continuous data exchange -> Option A
  4. Quick Check:

    WebSocket connection = persistent TCP [OK]
Quick Trick: WebSocket keeps TCP connection open for live data [OK]
Common Mistakes:
MISTAKES
  • Thinking WebSocket closes after each message
  • Confusing WebSocket with UDP protocol
  • Assuming manual reconnection needed after every message

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Raspberry Pi Quizzes