axum-impl-websockets

To implement concurrent Axum websockets, use `socket.split()` combined with `tokio::spawn` and `tokio::select!`. This prevents the sequential-only echo trap, allowing true bidirectional messaging for real-time chat or broadcast systems.

Migrating Axum websocket Message types from 0.7 to 0.8 requires changing payload construction and pattern matching from `String` and `Vec<u8>` to `Utf8Bytes` and `Bytes` to ensure type compatibility.

Axum websocket upgrades can fail silently if you omit the optional `on_failed_upgrade` callback. Implementing `WebSocketUpgrade.on_upgrade` alongside `on_failed_upgrade` ensures upgrade failures are visible.

Yes, you must enable the `ws` Cargo feature to use websockets in Axum. This feature gates the `WebSocketUpgrade` handler required to correctly wire and process WebSocket server endpoints.

Yes, you can combine Axum websockets with state and connection metadata like `ConnectInfo`. This allows you to build robust endpoints that track client details during bidirectional messaging.

The best way to structure a real-time chat hub using Axum websockets is applying a concurrent split+select loop pattern with `tokio::spawn` and utilizing version-aware 0.8 `Message` types for broadcasting.