5 ms·
I agree, it's not a mistake or a bug. It's an intentional feature, followed on with intentionally including the feature in further releases. It might not be a
by toast0 5y ago
I agree, it's not a mistake or a bug. It's an intentional feature, followed on with intentionally including the feature in further releases.
It might not be a great feature anymore, but it's not a bug. A 40 year old bug is things like TCP didn't have timeouts in all states, so LAST_ACK sockets should stay around forever if you follow the spec, or that if the two peers get mixed up about where the seq and ack are, each ack will elicit an ack from the other side, and if the peers are near enough to each other, that can result in gigabits of useless ack traffic that never results in data exchange (thankfully this isn't a common state; I've only seen it as a result of a bug in one OSes syncookies that was fixed, and it is likely to end with a timeout)