Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

HTTP/2 runs on top of a single TCP connection so it's still vulnerable to TCP ordering requirements.

TCP will probably never have a mainstream solution to this, better to switch to UDP or QUIC instead.



While I agree QUIC is a better long term solution[1], saying TCP ordering affects HTTP/2 is misleading. It is true, but it is quite easy to avoid bad behavior by using TCP_NOTSENT_LOWAT (also created by Google), to avoid HoL blocking. For example, SPDY had a similar problem which was ameliorated by only sending when the water mark is low enough:

https://insouciant.org/tech/prioritization-only-works-when-t...

[1] https://news.ycombinator.com/item?id=12282898




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: