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
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
The obligatory hello world thread!
Who are you and where are you from? :stuck_out_tongue:
New
I want to open this thread for you all to discuss and help those who really like Ash but are still hesitant to use it in a real project. ...
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
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
We’re evaluating API mocking tools for OpenAPI-based projects and would love to hear what other teams are using.
We’re particularly inte...
New
Is there a word for the ~> symbol used in Version strings?
Do you also just call it a Squiggle Arrow™ ?!
New
Other Trending Topics
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
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
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
There are three potential reasons for members of this forum to have a look at https://vutuv.de
You are tired or annoyed of LinkedIn.
Yo...
New
Latest Phoenix Threads
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
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #phoenix_html
- #elixirconf-us
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










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