WebSockets & Real-Time Communication

What considerations are important for implementing WebSocket heartbeat mechanisms?

class HeartbeatManager {
    constructor(ws, options = {}) {
        this.ws = ws;
        this.options = {
            pingInterval: 30000,
            pongTimeout: 5000,
            reconnectDelay: 3000,
            ...options
        };
        this.lastPong = Date.now();
    }

    start() {
        this.pingInterval = setInterval(() => {
            if (this.ws.readyState === WebSocket.OPEN) {
                this.ws.send('ping');
                this.waitForPong();
            }
        }, this.options.pingInterval);
    }

    waitForPong() {
        this.pongTimeout = setTimeout(() => {
            if (Date.now() - this.lastPong > this.options.pingInterval) {
                this.handleMissedPong();
            }
        }, this.options.pongTimeout);
    }

    handlePong() {
        this.lastPong = Date.now();
        clearTimeout(this.pongTimeout);
    }
}

Send heartbeats randomly
Don't implement heartbeats
Use configurable intervals with timeout handling
Important considerations for WebSocket heartbeat mechanisms include: 1) Configurable ping intervals based on network conditions, 2) Pong timeout handling, 3) Reconnection strategies for missed heartbeats, 4) Resource cleanup on connection loss, 5) Adaptive interval adjustment, 6) Network condition monitoring, 7) Load balancing impact consideration, 8) Proper error handling and logging, 9) Memory usage optimization, 10) Battery impact for mobile clients. The code demonstrates a robust heartbeat implementation with timeout handling and reconnection support.
Send heartbeats continuously

Next Question (17/17)