yolo007wizard
Does Phoenix have any plans to support channels with the new protocol coming up Webtransport / QUIC ? Seems like it would be great for liveview on lossy wireless connections.
I think this would require a new Phoenix pub/sub adapter but not sure.
Where Next?
Trending in Discussions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
derpycoder
QUIC is HTTP/2 replacement.
Channels just upgrade from HTTP/1 to Websockets.
I am not entirely sure CUIC will be used for sockets.
LostKobrakai
Before webtransport becomes supported we’d first need webserver libraries supporting http/3 (in a stable manner). It would need a new
Phoenix.Socket.Transportto support channels, but phoenix pubsub would be unaffected.yolo007wizard
Webtransport has very similar functionality to websockets but uses UDP/QUIC instead of TCP. Uni/Bi-directional multiplexed channels etc. Also reliable (tcp like) or unreliable (udp like) transport. Seems really cool imo
hauleth
That’s not correct. HTTP/3 is HTTP/2 replacement, QUIC is just yet another transport protocol. HTTP is L7 protocol while QUIC is L4.5-ish protocol. Completely different layers.
hst337
Yeah, because QUIC is SCTP replacement ha-ha. QUIC is almost 100% like SCTP over UDP
derpycoder
Hey I just replied QUICly, without much thought.
yolo007wizard
Well I’m not that technical yet with Elixir but it would be super cool to get a new Phoenix.Socket.Transport adapter for Webtransport.
Imagine the reliablilty of liveview apps from your phone. I would also think it relevant to the phoenix mobile stuff they’ve been experimenting with.
mtrudel
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.
mtrudel
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)
derpycoder
I should have read about WebTransport.
“Webtransport is designed as a ‘QUIC-native’ client-server communication protocol to replace websockets. You can think of it like websockets but better (faster handshake, it reuses the http2 / QUIC connection, and you can relax websocket’s reliability & ordering constraints). Or you can think of it as WebRTC, except way simpler for the 95% case where you want to communicate server/client.”
This is an, eye opening, excerpt I took from Ycombinator.
This is awesome.