Likely the first thing I’m planning on tackling in Bandit post-1.0 is QUIC support (with HTTP/3 / WebTransport support in Bandit coming soon thereafter). I’m expecting my first work to begin on this maybe March 2023, with some sort of early (QUIC) demo maybe later that summer. Absolutely no promises though.

The recent work in Phoenix 1.7 to factor out WebSocket support via the WebSock library was written with the intent of also support WebTransport when the time comes. Phoenix itself shouldn’t need to change for such support to land - it’s entirely on the underlying server to implement (see my last about Bandit’s plans for this)

I heard about WebTransport earlier this year while brushing up on WebSockets and LiveView. The multichannel support for both reliable and unreliable communication is going to be just what I need.

This feature allows you to do more with each connection, leading to richer communication between a greater number of simultaneous users. It means that you can send different types of content on different channels, so something like a large image could be sent over a different connection than other data, which would mean that the image can’t block chat communication.

What is WebTransport and can it replace WebSockets?

BTW, the WebSock behavior is glorious, @mtrudel & @axelson!