Re:What developers should know about TCP
by outworlder on Friday May 15, 2020 @02:10PM
(#23195367)
> I focused instead on the higher level stuff.
That's fine. But every developer should have a basic understanding of networking. But that can also be dangerous.
I still have people in the company who swear you can't have more than 65k incoming connections to a machine, because "that's how many ports there are". Don't get me started on all the misconceptions on TCP_TW_REUSE AND TCP_TW_RECYCLE. Lengthy discussions because apparently "TIME_WAIT is bad and uses up ports! "(see also, 65k). For context, these are servers, with multiple clients, from different source IPs.
That's fine. But every developer should have a basic understanding of networking. But that can also be dangerous.
I still have people in the company who swear you can't have more than 65k incoming connections to a machine, because "that's how many ports there are". Don't get me started on all the misconceptions on TCP_TW_REUSE AND TCP_TW_RECYCLE. Lengthy discussions because apparently "TIME_WAIT is bad and uses up ports! "(see also, 65k). For context, these are servers, with multiple clients, from different source IPs.