OvermindDL1
Well I made the old HTTP/2 thread, so I guess it’s time I should make the HTTP/3 thread, lol. ^.^;
Cloudflare has rolled out HTTP/3 support. Things from curl to chrome itself already support HTTP/3, and firefox is adding support in an upcoming nightly. So how goes HTTP/3 support in phoenix (does the BEAM even have a QUIC library yet speaking of)? ![]()
Trending in Discussions
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
Hi there! :wave:
@frigidcode and I (but mostly him) have been running an Elixir Book club, we’re almost done with Designing Elixir Syste...
New
I love Elixir. It’s one of 2 programming languages I’ve ever fallen in love with.
But I don’t use it anymore.
Serverless was the promis...
New
What IDE or editor are you using for Elixir development?
Personally, I use Zed, and I really like it, but sometimes I wish there were a ...
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
This was an interesting post by Jose. Curious to hear what others think. Evolving programming languages in the AI era - Dashbit Blog
Gen...
New
Hi there,
I’m in the process of deploying a Phoenix app to a EU host (UpCloud specifically), where the instances provided are mostly raw...
New
Other Trending Topics
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
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
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
In 2021 I started a new library called Tempo with the objective of modelling time as a set of intervals - not as instants. In 2022 I gave...
New
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
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #performance











Showing Posts 1 to 9- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
tristan
The most complete I’ve seen for QUIC is GitHub - g-andrade/quack: Erlang implementation of Google QUIC protocol · GitHub which has been archived. Since HTTP/3 moves parts for flow control to the protocol QUIC that were in the application level with HTTP/2 I have meant to look at if an http/2 library, like GitHub - joedevivo/chatterbox: HTTP/2 Server for Erlang. Boy, that guy was a real chatterbox waddn't he? I didn't think he was ever going to stop with the story. · GitHub, would make sense as a starting point to pull some parts out of for build quic.
Also, TLS 1.3 is required though, isn’t it? I know it is at least partially available in OTP 22 but I don’t know that all necessary components are available.
OvermindDL1
I’m unsure if referencing HTTP/2 would help. QUIC adds things that are a lot like SCTP style things like pipelines, and those are why some parts of HTTP/2 can be dropped, just because it already exists in QUIC, but it’s not specific to HTTP/# at all as it is just a protocol layer and QUIC is useful for non-HTTP things.
And I do know QUIC requires TLS, and I’m pretty sure TLS 1.3 is required but uncertain on that last part… Though I bet HTTP/3 requires it regardless.
pizzapim
QUIC does indeed require TLS 1.3 (https://quicwg.org/base-drafts/draft-ietf-quic-http.html). And if I remember it was only experimentally added in OTP recently.
I would also be interested in QUIC in Elixir
josevalim
Oh wow, that was QUIC.
hubertlepicki
@josevalim you definitely spend too much time chatting with @tenderlove, it influences your puns.
My 2 cents would be that in addition to server (as in Cowboy most likely), support for HTTP client would be a nice to have at some point. I can see this will be a big speed up in some systems I saw, that do crazy stuff like protobuf files stored & read through S3, once AWS adds support to HTTP/3 on their end.
OvermindDL1
Yeah it’s looking nice so far. I was hesitant about QUIC being a more ‘generic’ non-http standard at first but they even have things like unreliable channels in the spec now too, it looks very nice! Like becoming a modern SCTP replacement!
jonericcook
Hi @josevalim and @chrismccord, with http/3 getting closer to becoming an RFC are there any plans to incorporate it into the Elixir ecosystem?
Links for reference:
LostKobrakai
Neither José nor Chris maintain the webserver library used by phoenix.
This depends on cowboy:
https://github.com/ninenines/cowboy
lawik
For others that stumble in on this at some later date.
Cowboy is working on it?
https://github.com/ninenines/cowboy/issues/1544#issuecomment-957185586
Bandit is thinking about it and has it on the roadmap:
https://github.com/mtrudel/bandit/issues/28
https://github.com/mtrudel/thousand_island/issues/32