axum-websocket

Add real-time WebSocket support to your Axum app by wiring a handler that manages message upgrades, broadcast rooms, and heartbeat cycles. This standardizes text and binary frame handling and reduces boilerplate for real-time features like chat and live feeds.

Broadcast WebSocket messages to multiple clients in Rust using tokio::sync::broadcast channels within Axum routes. This pattern creates broadcast rooms that efficiently distribute live updates or pub/sub events across all connected clients per room.

Manage per-connection state in an Axum WebSocket handler by implementing stateful upgrades with dedicated AppState for each connection. This isolates connection-specific data and logic, enabling robust multi-route real-time features and individual client tracking.

Axum WebSocket connections drop unexpectedly without active keep-alive signals. Implement a heartbeat mechanism using Tokio intervals to periodically ping clients and manage proper close codes, maintaining healthy connections and detecting dead peers.

Yes, this WebSocket Skill explicitly supports Axum 0.8 and standardizes correct Message type usage, differentiating between Utf8Bytes/Text and Binary frames. It ensures proper close-code handling and reduces type-mismatch errors during real-time communication.

The best way to handle WebSocket close codes in an Axum application is to standardize explicit close-code management within your handler logic. Proper close-code handling ensures clean connection termination and prevents resource leaks in real-time pub/sub systems.