yolo007wizard
Webtransport / QUIC for Phoenix channels?
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.
Trending in Discussions
As the title says, please share what you’ve been up to with Elixir. Whether that’s been learning it, looking into it, making stuff with i...
New
@chrismccord : I just saw the Extract AGENTS.md from Phoenix.new into phx.new generator commit to the phoenix project.
My initial shotgu...
New
I was working on an Ecto migration and I needed a timestamp. So, for the nth time, I looked up the different data types for timestamps, a...
New
Just a general thread to post chat/news/info relating to AI/ML stuff that may be relevant for Nx now or in the future. Got anything to sh...
New
I just stumbled on a newly redesigned elixir-lang.org. :tada: It looks like @Software_Mansion did the work, and I think it is generally a...
New
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
Fly’s CEO posted this recently - Turn And Face The Strange · The Fly Blog
It says that Fly is going all-in on sprites, which is a worry ...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
@hugobarauna and I (Alex Koutmos) have been hard at work on writing a book on Nerves that takes you from simply blinking LEDs to building...
New
We want to introduce a new native datatype to Erlang: native records. Although replacing all tuple records with native records is not our...
New
Latest Phoenix Threads
Chat & Discussions>Discussions
Latest on Elixir Forum
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #performance










First 10 of 12 Posts
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.