4 ms·
Because TCP was designed as a single-stream protocol. There's SCTP which operates with messages rather than streams and can send those messages simultaneously.
by vbezhenar 8y ago
Because TCP was designed as a single-stream protocol. There's SCTP which operates with messages rather than streams and can send those messages simultaneously.
- amelius 8y agoSounds interesting. Is that implemented in kernels? And why wasn't HTTP1.1+ built on top of that?
- sanxiyn 8y agoYes, SCTP is implemented in kernels.
- deleted 8y ago[deleted]
- Volundr 8y agoPretty much any modern OS supports SCTP. HTTP wasn't built off it because HTTP came long before SCTP, but you won't find many protocols built off SCTP anyway, because it's poorly supported by middle-boxes and firewalls. Just look at any cloud firewall for example, you can open TCP or UDP, but not SCP or any of the "lesser known" protocols. It's currently in an unfortunate chicken and egg problem, where crappy firewalls don't support it because it's rarely used, and it's rarely used because crappy firewalls don't support it, but are everywhere on the public internet. HTTP3 actually does propose changing the transport protocol, but to QUIC, which is a transport over UDP.
- lttlrck 8y agoSCTP can be tunneled over UDP - which WebRTC does. It didn’t get the right traction. It isn’t built into windows, it was even a second class citizen on Linux not that long ago requiring lksctp to be installed (maybe it still does).
- duskwuff 8y ago> Is that implemented in kernels? Yes, but it's largely unusable because it's not supported by most home network routers, and isn't supported at all on Windows or macOS. > And why wasn't HTTP1.1+ built on top of that? Because it didn't exist yet. HTTP 1.1 was standardized in 1997, and SCTP development didn't start until around 2000.