0Pricing
Real-Time Streaming Systems (WebRTC + Live Data) · Aula

Server-Sent Events (SSE) para envio unidirecional

Explore os Server-Sent Events (SSE) como uma alternativa mais simples aos WebSockets para enviar atualizações de dados unidirecionais do servidor para o cliente.

Server-Sent Events (SSE) para envio unidirecional é uma aula grátis de Real-Time Streaming Systems (WebRTC + Live Data) no CoddyKit. Esta é a aula 3 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Real-Time Streaming Systems (WebRTC + Live Data), e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Real-Time Streaming Systems (WebRTC + Live Data) inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

Intro to Server-Sent Events

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.

SSE: Simpler Unidirectional Push

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.

How SSE Connections Work

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.

Listening with EventSource

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:

const eventSource = new EventSource('/stream');

eventSource.onmessage = (event) => {
  console.log('New data:', event.data);
  // Update your UI here
};

eventSource.onerror = (error) => {
  console.error('SSE Error:', error);
  eventSource.close(); // Close connection on error
};

Building an SSE Server

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.

const http = require('http');

http.createServer((req, res) => {
  res.writeHead(200, {
    'Content-Type': 'text/event-stream',
    'Cache-Control': 'no-cache',
    'Connection': 'keep-alive'
  });

  // Send a message every second
  const intervalId = setInterval(() => {
    res.write('data: The time is ' + new Date().toLocaleTimeString() + '\n\n');
  }, 1000);

  // Clean up on client disconnect
  req.on('close', () => {
    clearInterval(intervalId);
    res.end();
  });

}).listen(8080, () => {
  console.log('SSE server running on http://localhost:8080');
});

Sending Custom SSE Event Types

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).

const http = require('http');

http.createServer((req, res) => {
  res.writeHead(200, {
    'Content-Type': 'text/event-stream',
    'Cache-Control': 'no-cache',
    'Connection': 'keep-alive'
  });

  let counter = 0;
  const intervalId = setInterval(() => {
    if (counter % 2 === 0) {
      res.write('event: heartbeat\n');
      res.write('data: Ping! ' + counter + '\n\n');
    } else {
      res.write('event: update\n');
      res.write('data: New data point: ' + Math.random().toFixed(2) + '\n\n');
    }
    counter++;
  }, 2000);

  req.on('close', () => {
    clearInterval(intervalId);
    res.end();
  });

}).listen(8080, () => {
  console.log('SSE server (custom events) running on http://localhost:8080');
});

Automatic Reconnection Magic

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.

Benefits of Using SSE

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.

SSE Limitations

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).

Real-World SSE Examples

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.

SSE Quick Check

Time to test your understanding of Server-Sent Events!

Lesson Summary: SSE

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!

Perguntas Frequentes

A aula “Server-Sent Events (SSE) para envio unidirecional” é grátis?

Sim — o texto completo de “Server-Sent Events (SSE) para envio unidirecional” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Real-Time Streaming Systems (WebRTC + Live Data), atualize para CoddyKit PRO. O curso de Real-Time Streaming Systems (WebRTC + Live Data) inclui 4 aulas no total.

O que vou aprender em “Server-Sent Events (SSE) para envio unidirecional”?

Explore os Server-Sent Events (SSE) como uma alternativa mais simples aos WebSockets para enviar atualizações de dados unidirecionais do servidor para o cliente. Você pratica Real-Time Streaming Systems (WebRTC + Live Data) com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar Real-Time Streaming Systems (WebRTC + Live Data)?

Nenhuma experiência prévia é necessária. Real-Time Streaming Systems (WebRTC + Live Data) no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 3 de 4.

Quanto tempo leva a aula “Server-Sent Events (SSE) para envio unidirecional”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de Real-Time Streaming Systems (WebRTC + Live Data)?

Sim. Cada aula de Real-Time Streaming Systems (WebRTC + Live Data) inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Dados ao vivo versus HTTP tradicional
  2. WebSockets para fluxo bidirecional
  3. Server-Sent Events (SSE) para envio unidirecional
  4. Sondagem Longa e a Evolução para a Transmissão por Fluxo
← Voltar para Real-Time Streaming Systems (WebRTC + Live Data)