Grundlagen des WebSocket-Protokolls

Modern web applications often need instant updates and real-time interactions. Think of live chats, multiplayer games, or collaborative editing tools.

Traditional HTTP wasn't designed for this. That's where WebSockets come in!

In this lesson, you'll learn what WebSockets are and why they're crucial for building dynamic, real-time features.

HTTP (Hypertext Transfer Protocol) works on a simple request-response model:

• The client sends a request.
• The server sends a response.

Once the response is sent, the connection closes. This is efficient for fetching static content, but not for continuous, instant data exchange.

To get "real-time" updates with HTTP, developers often used:

• Polling: Client repeatedly asks the server for new data. This is inefficient and can cause high latency.
• Long Polling: Server holds the connection open until new data is available or a timeout occurs, then responds. Better, but still not truly bidirectional or instant.

Both methods introduce significant overhead and delay for real-time needs.

The WebSocket protocol (using ws:// or wss:// for secure connections) provides a full-duplex communication channel over a single, long-lived TCP connection.

Think of it as a persistent, open phone line between a client and a server, rather than sending a new letter for every message.

A WebSocket connection begins with a standard HTTP request, but with an important header:

This tells the server the client wants to "upgrade" the connection. If the server agrees, it responds with a 101 Switching Protocols status, and the connection transforms into a WebSocket connection.

This initial HTTP request and response is called the handshake. Once successful, the underlying TCP connection remains open, and both client and server can send data frames over it.

This means no more HTTP headers for every individual message – just the raw data, making communication very efficient.

Unlike HTTP's client-server, request-response flow, WebSockets offer bidirectional (or full-duplex) communication. This means:

• The client can send data to the server at any time.
• The server can send data to the client at any time.

This two-way street is fundamental for truly interactive, real-time applications.

WebSockets bring several key benefits for real-time applications:

• Lower Latency: Instant data transfer without polling delays.
• Reduced Overhead: Minimal header data after the initial handshake.
• Efficiency: A single, persistent connection saves resources.
• True Real-time: Immediate updates and interactions.

You'll find WebSockets powering many modern applications:

• Chat Apps: Instant message delivery.
• Live Feeds: Sports scores, stock tickers, news updates.
• Multiplayer Games: Real-time player interactions.
• Collaborative Tools: Shared whiteboards, document editing.
• IoT Devices: Real-time sensor data streaming.

Which of the following are true characteristics of the WebSocket protocol?

Great job! You've grasped the fundamentals of the WebSocket protocol.

• We saw how traditional HTTP struggles with real-time needs.
• Learned that WebSockets provide a persistent, full-duplex communication channel.
• Understood the importance of the HTTP handshake to "upgrade" a connection.
• Explored its advantages for low-latency, efficient, and truly real-time applications.

Next, we'll dive into implementing WebSockets with FastAPI!