Gestione delle disconnessioni e riconnessioni
Implementi la logica lato client e lato server per rilevare le disconnessioni e tentare automaticamente la riconnessione.
Gestione delle disconnessioni e riconnessioni è una lezione WebSockets & Realtime Systems Programming gratuita su CoddyKit. Questa è la lezione 1 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento WebSockets & Realtime Systems Programming, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso WebSockets & Realtime Systems Programming include 4 lezioni in totale.
Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.
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.
Impara WebSockets & Realtime Systems Programming con un tutor IA — gratis
Scrivi ed esegui vero codice nel tuo browser, ricevi aiuto istantaneo da un tutor IA disponibile 24/7, e riprendi da dove hai lasciato sul web o nell'app.
- Corsi
- 12
- Lezioni
- 47
Domande Frequenti
La lezione «Gestione delle disconnessioni e riconnessioni» è gratuita?
Sì — il testo completo di «Gestione delle disconnessioni e riconnessioni» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso WebSockets & Realtime Systems Programming, passa a CoddyKit PRO. Il corso WebSockets & Realtime Systems Programming include 4 lezioni in totale.
Cosa imparerò in «Gestione delle disconnessioni e riconnessioni»?
Implementi la logica lato client e lato server per rilevare le disconnessioni e tentare automaticamente la riconnessione. Eserciti WebSockets & Realtime Systems Programming con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.
Ho bisogno di esperienza per iniziare WebSockets & Realtime Systems Programming?
Non è richiesta alcuna esperienza precedente. WebSockets & Realtime Systems Programming su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 1 di 4.
Quanto tempo richiede la lezione «Gestione delle disconnessioni e riconnessioni»?
La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.
Posso scrivere ed eseguire codice in questa lezione WebSockets & Realtime Systems Programming?
Sì. Ogni lezione WebSockets & Realtime Systems Programming include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.
Tutte le lezioni di questo corso
- Gestione delle disconnessioni e riconnessioni
- Propagazione e ripristino robusti degli errori
- Heartbeat e Keep-Alive
- Conferma dei messaggi e garanzie di consegna