# HTTP/3: Everything you need to know about the next-generation web protocol

**URL:** <https://forum.devtalk.com/t/http-3-everything-you-need-to-know-about-the-next-generation-web-protocol/40481>\
**Category:** In The News\
**Tags:** quic, http, web\
**Created:** [13 February 2022 14:37 UTC](https://forum.devtalk.com/t/http-3-everything-you-need-to-know-about-the-next-generation-web-protocol/40481 "2022-02-13T14:37:57Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![OvermindDL1](https://forum.devtalk.com/user_avatar/forum.devtalk.com/overminddl1/32/52_2.png) [@OvermindDL1](https://forum.devtalk.com/u/OvermindDL1)\
**Post date:** [15 February 2022 22:28 UTC](https://forum.devtalk.com/t/http-3-everything-you-need-to-know-about-the-next-generation-web-protocol/40481/3 "2022-02-15T22:28:53Z")

</div>

I really like the QUIC protocol. It’s multiple reliable channels and built-in security is awesome. We can still do ‘unreliable’ channels via normal UDP (though I wish we could have unreliable channels in QUIC so we wouldn’t have to manage a secondary set of encryption). What I wish it had were an unordered channel, where you could send small packets that would be guaranteed to be received but the order doesn’t matter, rather just as fast as possible is what matters and for them to ‘eventually’ arrive, it especially could keep the held memory open for the buffered data smaller as well as the increased speed.

---

_[View the full topic](https://forum.devtalk.com/t/http-3-everything-you-need-to-know-about-the-next-generation-web-protocol/40481)._
