1 views collected around this technical thread.
This article explains the core characteristics of TCP and UDP, compares their reliability and connection models, clarifies the concept and range of port numbers, and demonstrates that both protocols can share the same port without conflict, illustrated with real‑world examples such as DNS.
The article explains how TCP connections are identified by a four‑tuple, why the theoretical maximum client connections are 65,535 due to port limits, how servers can theoretically handle up to 2⁴⁸ connections, and why real‑world concurrency is constrained by memory, file descriptors and port reuse rather than the 65535 port count.
The article explains how TCP connections are identified by a four‑tuple, clarifies the theoretical maximum of 65,535 client ports versus the far larger possible server connections, and discusses practical limits imposed by memory, file descriptors, and system configuration on Linux servers.
The article explains how TCP connections are identified by a four‑tuple, why the theoretical maximum of 65,535 client ports does not cap server concurrency, and how real‑world limits are governed by memory, file‑descriptor counts, and port reuse techniques.
This article provides a comprehensive introduction to the transport layer of computer networks, explaining the roles of TCP and UDP, socket APIs, port numbers, multiplexing, packet structures, connection management, three‑way handshake, four‑way termination, and congestion‑control mechanisms.
This article provides a comprehensive overview of the transport layer in the TCP/IP model, explaining the roles of TCP and UDP protocols, socket APIs, port numbers, multiplexing, and how data is encapsulated and transmitted between end systems.