Server-Sent Events (SSE) สำหรับการส่งข้อมูลทางเดียว

Welcome! In this lesson, we'll explore Server-Sent Events (SSE), a powerful yet simple way for servers to push real-time updates to clients.

Unlike traditional HTTP requests where the client always asks the server for data, SSE allows the server to send data to the client whenever new information is available, without the client needing to constantly poll.

You might be familiar with WebSockets for real-time communication. While WebSockets enable full two-way communication, SSE is designed specifically for unidirectional data flow, from the server to the client.

This makes SSE a simpler and often more efficient choice for scenarios where the client only needs to receive updates, not send them back in real-time.

SSE operates over a standard HTTP connection. The client initiates a regular HTTP request, but the server responds with a special Content-Type: text/event-stream header.

Instead of closing the connection after sending data, the server keeps it open. It then pushes new data to the client whenever updates are ready, effectively streaming events over this single, persistent connection.

On the client-side (typically in a web browser), you use the built-in EventSource API to connect to an SSE stream and listen for incoming events.

Here's a basic JavaScript snippet to connect to an SSE endpoint and log messages:

Let's see how a simple server can send SSE messages. This Node.js example creates an HTTP server that sends the current time every second.

Run this code, then open a browser and navigate to http://localhost:8080 to see the events stream in your console.

Beyond the default message event, SSE allows you to define custom event types using the event: field. This helps clients handle different kinds of updates differently.

On the client, you'd use eventSource.addEventListener('myCustomEvent', handler).

One of the most convenient features of EventSource is its built-in automatic reconnection. If the connection drops (due to network issues, server restart, etc.), the browser will automatically attempt to reconnect after a short delay.

You don't need to write any extra code to handle connection failures and retries, making SSE very robust for continuous updates.

SSE offers several compelling advantages for server-to-client push:

• Simplicity: Easier to implement than WebSockets for one-way data.
• Built-in Reconnection: Automatic handling of connection drops by EventSource.
• HTTP Compatibility: Works over standard HTTP/HTTPS, compatible with existing infrastructure (proxies, firewalls).
• HTTP/2 Multiplexing: Can share a single connection with other HTTP requests efficiently.

While powerful, SSE isn't suitable for all real-time scenarios:

• Unidirectional Only: Only supports server-to-client communication. For client-to-server or true bidirectional, WebSockets are required.
• No Binary Data: Limited to UTF-8 encoded text. You cannot send raw binary data directly via SSE.
• Browser Connection Limits: Browsers typically limit the number of concurrent SSE connections per domain (e.g., 6).

SSE shines in applications that need continuous, one-way updates:

• Live Stock Tickers: Continuously pushing price updates to trading dashboards.
• News Feeds: Instant delivery of breaking news or article updates.
• Activity Streams: Real-time notifications (e.g., new emails, social media activity).
• Dashboards: Live updates for monitoring system metrics or user statistics.

Great job! You've now learned about Server-Sent Events (SSE).

• SSE enables unidirectional, server-to-client data push over a single HTTP connection.
• It's simpler than WebSockets for one-way updates and features automatic reconnection.
• You use the client-side EventSource API to listen for events.
• SSE is perfect for live dashboards, news feeds, and real-time notifications.

Keep exploring how these live data architectures can enhance your applications!