This article explains why TCP requires a three‑way handshake instead of two, details the six TCP flag bits, clarifies sequence and acknowledgment numbers, walks through each handshake step with example numbers, and describes the four‑way termination process and related timing considerations.
This article investigates MySQL binlog numbering, discovers that the maximum sequence number is 2^31‑1 (2147483647), shows through three experiments how MySQL behaves when approaching or hitting this limit, and explains the resulting warnings and server shutdown.
This article provides a comprehensive overview of the TCP protocol, covering its role in the network stack, packet size limits, sequence numbering, how operating systems reassemble packets, the slow‑start mechanism, ACK handling, and strategies for detecting and recovering from lost packets.
This article analyzes why instant‑messaging (IM) messages can arrive out of order due to time discrepancies, network behavior, and multithreading, and proposes a comprehensive design using global sequence numbers, channel‑aware routing, client‑side caching, and ACK‑based flow control to guarantee ordered delivery.
This article explains the principles behind TCP's three‑way handshake and four‑way teardown, covering connection establishment, data transfer, termination, header fields, state diagrams, sequence‑number wraparound, SYN‑flood attacks, mitigation techniques, and a practical Redis packet‑capture analysis, all illustrated with diagrams and code snippets.
