5 ms·
Problem with rolling your own TCP stack is all the RFCs that compose what we collectively know as TCP. Congestion control and flow control for instance, there
by partycoder 9y ago
Problem with rolling your own TCP stack is all the RFCs that compose what we collectively know as TCP.
Congestion control and flow control for instance, there are many RFCs that define them.
- corysama 9y agoI like the explanation I've heard that rolling your own TCP stack is a very educational and worthwhile experience. But, what makes TCP so difficult in practice is that there are so many home-rolled stacks out there in the wild that all have different quirks and errors. So yes, please roll your own. But no, please do not add to the wild zoo of errors by deploying it.
- zik 9y agoThat's literally how the original TCP/IP implementations were tested: by running them against each other in "bake-offs": https://tools.ietf.org/html/rfc1025 https://tools.ietf.org/html/rfc1025 I think there's a lot to be said for testing network code against the myriad of real world implementations out there.
- saminiir 9y agoVery interesting and yes, interoperability is hard. https://www.snellman.net/blog/archive/2014-11-11-tcp-is-harder-than-it-looks.html https://www.snellman.net/blog/archive/2014-11-11-tcp-is-hard...