4 ms·
We can't really blame Linux for this, this is a networking protocols problem. It's their stack of hacks.
by oblio 5y ago
We can't really blame Linux for this, this is a networking protocols problem.
It's their stack of hacks.
- ratorx 5y agoWell only sort of. As far as I understand, nothing about TCP means that ports can be reused, or that 0.0.0.0 has special meaning, or that processes can’t listen on the same port, or IPv4 to IPv6 delivery etc. These are all operating system design choices, some of which stem from the sockets API. I’m pretty sure you could design a spec-compliant alternative which didn’t do any of these things, if you really wanted to.
- wyager 5y agoTCP and UDP don't really dictate any of this behavior. Most of these hacks are the result of design choices in Linux and the socket API - abstractions on top of TCP/UDP that aren't the only option. In my experience, the network layer is often way better-designed, more reliable, more interoperable, and less hacky than most OS abstractions built on top of it.