Gestión de desconexiones y reconexiones
Implemente la lógica del cliente y del servidor para detectar desconexiones e intentar reconectarse automáticamente.
Gestión de desconexiones y reconexiones es una lección gratuita de WebSockets & Realtime Systems Programming en CoddyKit. Esta es la lección 1 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de WebSockets & Realtime Systems Programming, y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de WebSockets & Realtime Systems Programming incluye 4 lecciones en total.
Partes de esta lección aún no han sido traducidas y se muestran en inglés.
Why Connections Drop
In the real world, network connections aren't always perfect. WebSockets, despite being persistent, can break due to many reasons.
Ignoring these disconnections can lead to unresponsive applications and a poor user experience. This lesson explores how to gracefully handle these interruptions.
Causes of Connection Loss
What makes a WebSocket connection drop?
- Network Issues: Wi-Fi drops, internet outages, proxy problems.
- Server Restarts: The server application might restart for updates or maintenance.
- Client Offline: The user closes their browser, loses power, or puts their device to sleep.
- Idle Timeouts: Some proxies or firewalls might close idle connections.
Client Detects Disconnects
On the client side, the browser's native WebSocket API provides events to notify you about connection status changes.
The most important event for detecting a disconnection is the onclose event. It fires when the connection is either gracefully closed by the server or abruptly lost.
Simple Reconnect Attempt
When onclose fires, you can immediately try to reconnect. This simple approach works for temporary glitches but can be problematic.
Try running this basic client-side example:
let ws;
function connect() {
ws = new WebSocket("ws://localhost:8080");
ws.onopen = () => console.log("Connected!");
ws.onmessage = (event) => console.log("Received:", event.data);
ws.onerror = (error) => console.error("WebSocket Error:", error);
ws.onclose = () => {
console.log("Disconnected. Reconnecting...");
setTimeout(connect, 1000); // Try again in 1 second
};
}
connect();Why Simple Retries Fail
Continuously trying to reconnect immediately (e.g., every 1 second) can overwhelm both the client and the server.
- Client Resource Drain: Constant connection attempts consume CPU and network resources.
- Server Overload: If many clients disconnect and then flood the server with reconnect requests, it can lead to a Denial of Service (DoS) situation.
- No Backoff: It doesn't account for prolonged outages.
Smart Reconnection: Backoff
To prevent overloading and provide a better experience, we use reconnection backoff strategies.
A backoff strategy introduces delays between reconnection attempts, and these delays typically increase with each failed attempt. This gives the server time to recover and prevents a "thundering herd" problem.
Exponential Backoff Logic
Exponential backoff is a common and effective strategy. It means the delay between retries increases exponentially.
- First retry: 1 second
- Second retry: 2 seconds
- Third retry: 4 seconds
- Fourth retry: 8 seconds
You usually cap the maximum delay to prevent excessively long waits and add some random "jitter" to avoid synchronized retries.
Client with Exponential Backoff
Let's enhance our client-side code to use exponential backoff with a maximum delay and some random jitter. Try running it!
let ws;
let reconnectInterval = 1000; // Start with 1 second
const maxReconnectInterval = 30000; // Max 30 seconds
let reconnectTimer;
function connect() {
ws = new WebSocket("ws://localhost:8080");
ws.onopen = () => {
console.log("Connected!");
reconnectInterval = 1000; // Reset on successful connection
clearTimeout(reconnectTimer);
};
ws.onmessage = (event) => console.log("Received:", event.data);
ws.onerror = (error) => console.error("WebSocket Error:", error);
ws.onclose = () => {
console.log(`Disconnected. Retrying in ${reconnectInterval / 1000}s...`);
reconnectTimer = setTimeout(connect, reconnectInterval);
reconnectInterval = Math.min(reconnectInterval * 2, maxReconnectInterval);
// Add some random jitter (e.g., +/- 10%) for better distribution
reconnectInterval += (Math.random() - 0.5) * reconnectInterval * 0.2;
reconnectInterval = Math.floor(reconnectInterval);
};
}
connect();Server-Side Disconnects
The server also needs to know when a client disconnects. This is crucial for cleaning up resources, updating connected user lists, or stopping data streams for that client.
Using a library like ws in Node.js, the WebSocket server emits a 'close' event on the individual client connection object when it disconnects.
Server Cleanup on Disconnect
Here's a basic Node.js WebSocket server example showing how to handle client disconnections and remove them from an active connections list.
const WebSocket = require('ws');
const wss = new WebSocket.Server({ port: 8080 });
let clients = new Set();
wss.on('connection', function connection(ws) {
clients.add(ws);
console.log('Client connected. Total:', clients.size);
ws.on('message', function incoming(message) {
console.log('received: %s', message);
});
ws.on('close', function close() {
clients.delete(ws);
console.log('Client disconnected. Total:', clients.size);
});
ws.send('Welcome!');
});
console.log('WebSocket server started on port 8080');Check Your Understanding
Consider a client-side WebSocket application that needs to handle disconnections robustly.
Which of the following are good practices for implementing a reconnection strategy?
Recap: Robust Connections
We've explored how crucial it is to handle disconnections in realtime applications. Both client and server play a role in maintaining connection resilience.
- Clients use
oncloseto detect disconnections. - Exponential backoff with jitter and a max delay prevents server overload during reconnections.
- Servers use
on('close')to clean up resources when clients leave.
These strategies ensure your realtime apps remain responsive and reliable, even in unstable network conditions.
Preguntas frecuentes
¿La lección «Gestión de desconexiones y reconexiones» es gratis?
Sí — el texto completo de «Gestión de desconexiones y reconexiones» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de WebSockets & Realtime Systems Programming, actualiza a CoddyKit PRO. El curso de WebSockets & Realtime Systems Programming incluye 4 lecciones en total.
¿Qué aprenderé en «Gestión de desconexiones y reconexiones»?
Implemente la lógica del cliente y del servidor para detectar desconexiones e intentar reconectarse automáticamente. Practicas WebSockets & Realtime Systems Programming con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.
¿Necesito experiencia previa para empezar WebSockets & Realtime Systems Programming?
No se requiere experiencia previa. WebSockets & Realtime Systems Programming en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 1 de 4.
¿Cuánto tiempo toma la lección «Gestión de desconexiones y reconexiones»?
La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.
¿Puedo escribir y ejecutar código en esta lección de WebSockets & Realtime Systems Programming?
Sí. Cada lección de WebSockets & Realtime Systems Programming incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.
Todas las lecciones de este curso
- Gestión de desconexiones y reconexiones
- Propagación y recuperación robustas de errores
- Heartbeats y mantenimiento de conexiones
- Confirmación de mensajes y garantías de entrega