Repository navigation
HTTP/3 support #38478
Description
Activity
Opening a tracking issue is perfectly fine :)
And yes, I'm working on reintroducing quic and http3 now. It's going to take a bit of time since it's not the only thing I have on my plate at the moment but it is coming. I'll provide a more detailed update later today
Reacted by Benjamin Gruenbaum, Per Bernhardsson, Alberto Esposito, Ramsundhar Madhavan, Robin Marx, bl-ue, Linz, rustalot, Paulo Coghi, Jairus and 26 moreReacted by Michael Rommel, Stephen Belanger, Alberto Esposito, Ramsundhar Madhavan, bl-ue, Linz, rustalot, Paulo Coghi, Jairus, ignoramous and 19 moreGreat work on this @jasnell. Looking forward for your contribution in developing this. In this latest era of remote worlds (thanks to COVID), the need for this QUIC & HTTP/3 support in Nodejs is undeniable.
Let me know if you need some assitance.
Work is underway. I'm reworking the underlying impl. Expect an update in about a week
Reacted by René Kilczan, bl-ue, Trygve Lie, Sylvain Dumont, Gary Crye, Shrujal Shah, Arin, loukkyy, Alberto Esposito, Luca Mathaea and 23 moreHi @jasnell, I guess you have a lot to do at nearforms. Are there any updates on this issue? Or is it already possible to somehow do experimental QUIC based application implementations within its current state in node.js?
Reacted by Michael Rommel@boaerosuke I think this is becoming a blocker for this issue, so work is still progressing.
Reacted by Eridy Lukau, Linz and BeckWork is still progressing. Slow going, but moving forward.
Reacted by Nicolas HENRY, Alberto Esposito, André Ribeiro, Szymon Marczak, Chen Ozer, Shahar Ziv, Linz, Nick K., Eridy Lukau, Daniel Lockyer and 20 moreReacted by Linz, rustalot, Shahar Ziv, Momen, Tom Klein, Nouvistiardi Azra, PlopTheReal, Beck, lin72h, dnalborczyk and 3 moreReacted by Linz, Trygve Lie, rustalot, René Kilczan, Tim Perry, Dídac García, Shahar Ziv, Momen, Tom Klein, Sachin Rana and 14 moreReacted by Szymon Marczak, Chen Ozer, Shahar Ziv, Linz, Nick K., rustalot, Tim Perry, Alberto Esposito, Momen, Tom Klein and 9 moreThanks for your feedback! Absolutely appreciating your work!
rustalot has contributed $75.00 to this issue on Rysolv.
The total bounty is now $75.00. Solve this issue on Rysolv to earn this bounty.Reacted by Adam DunstanHey @jasnell, feel free to remove if off topic. I added a bounty on this issue. Understandably it's more that $75 worth of work, but wanted to chip in towards your work.
Reacted by Alberto Esposito, Aravind Nair, Frazer Smith, ignoramous, Peter Ahlers, Tho Arrow, Mateusz Rębacz, Vinson Chuong, dataknowsJson and Valerii PetryniakAn anonymous user has contributed $50.00 to this issue on Rysolv.
The total bounty is now $125.00. Solve this issue on Rysolv to earn this bounty.Reacted by Adam Dunstan, Vinson Chuong, Yoseph Maguire and Théo LUDWIGJust an update... the basic support is implemented. The PR is ready for review tho overall it's still far from done.
Reacted by Shahar Ziv, liuyanjie, André Ribeiro, Alberto Esposito, Paulo Coghi, ignoramous, Ilyess Zenasni, Ashish, Vinson Chuong, Rodrigo Moreno and 6 more40 remaining items
I'm noob enough to make it go above from my head but after reading comments I can understand its still in process xD
Let see how next web protocol will feel in upcoming node versions@jasnell @bnoordhuis It might be good to lock this thread.
Reacted by Jan Vlnas, Rafael Gawenda, Charlie Simms and douiraReacted by 沈鸿飞, Pivigor, David P, Tim Perry, Alberto Esposito, Victor Campa, pixel-toys-chris-evans, Chris Calo, Trackhe, Theo Paris and 5 moreReacted by Jordan BaczukI have a few thoughts and suggestions regarding the project's current status and potential improvements. Firstly, I'm curious about the decision to lock the project while it's still being worked on. Could you kindly clarify if it's nearing completion or if there are plans to continue development?
Secondly, it would be incredibly helpful to access an example to understand the implementation better. Could you please provide some guidance on where we can find a hands-on example?
Additionally, I've noticed that Google already employs h3 in all of its websites, which appears to be working quite effectively for them. As a game developer, I've experienced firsthand how UDP can offer significant speed advantages over TCP, although it does come with some reliability challenges. However, with real-time corrections, UDP can work remarkably well for games. Considering this, I wonder why we haven't explored its potential for websites earlier. Perhaps integrating it as the standard and out-of-the-box option when using Express.js, for instance, could bring about interesting benefits to man-kind.
I'm here, along with other community members, ready to assist with any programming issues and offer solutions in various languages. It's evident that Express.js has already outperformed Flask in all performance benchmarks, and I believe we should continue supporting its progress rather than leaving it behind. This project has the potential to make a positive impact, and I'm surprised that it has received relatively modest funding so far. It would be incredible if influential figures like Bill Gates could recognize the significance of this work and contribute to its success with substantial donations.
Moreover, I strongly believe that adopting such improvements could contribute to reducing CO2 emissions and foster a better world. Let's collaborate and work towards making this project reach its full potential."
Reacted by BurgilReacted by BurgilReacted by BurgilReacted by BurgilReacted by Burgil- locked as too heated and limited conversation to collaborators
on Jul 23, 2023 The basic implementation of http/3 support is in. Still extremely experimental but generally functional. Expect bugs. See the suite of tests in
test/parallel/test-quic-h3-*for examples.Overview of the HTTP/3 support... https://www.jasnell.me/posts/quic-part-4
Given the work in progress, I don't think we actually need to keep this issue open further.
As far as I can tell, there's currently no open issue explicitly tracking for QUIC or HTTP/3. Selfishly I'm very interested in knowing when this is available, so I'd personally find it very valuable to have an issue (this issue) tracking the current state and progress.
To document the current state:
@jasnell I think you've been doing most of the legwork here (thank you!), is that about right?
Feel free to close this if it's a problem to create feature requests like this, but I suspect there's likely to be lots of people interested in QUIC & HTTP/3, so a central issue documenting it is pretty useful imo.