HTTP/3 support

[pimterry]

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:

• QUIC was tracked in https://github.com/nodejs/node/issues/23064
• That was closed when the experimental implementation was started
• That entire implementation was later removed due to lack of support in OpenSSL
• We've now moved to the Quictls fork of OpenSSL to avoid being blocked by OpenSSL's approach to implementing QUIC
• There's a draft QUIC implementation being worked on here.
• That QUIC implementation is a prerequisite for any HTTP/3 implementation (so we're still a way off)

@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.

[espoal]

@clshortfuse a proof of concept was already delivered in node 17 if I was not wrong, but due to issues it was removed.

[SwapnilSoni1999]

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

[orderplatform-edward]

Any news ? still waiting :D

[mreinstein]

@jasnell @bnoordhuis It might be good to lock this thread.

[burgil]

I 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."

[jpike88]

using any programming language you prefer

How dare you!

[burgil]

Well I guess that includes cpp I don't think the whole codebase is nodejs lol