TCPIP Illustrated, Volume 3 TCP for Transactions, HTTP, NNTP, and the UNIX Domain Protocols (W. Richard Stevens)（Z-Library）

【One-Line Pitch】 A deep, protocol-level tour of TCP for transactions plus the application protocols that ride on top of it—HTTP, NNTP, and the UNIX domain protocols—for engineers who already know TCP/IP basics and want to understand how real systems use them. Best for network programmers, systems engineers, and anyone debugging or designing protocols rather than just configuring them. 【Book Arc】 - **Opening (~0%–20%)**: Establishes the motivation for T/TCP—standard TCP's three-way handshake and TIME_WAIT costs for short, transactional exchanges—and frames the problem this volume solves. - **Early (~20%–40%)**: Introduces the T/TCP extensions themselves: the mechanisms that let a client open a connection, send data, and close it in fewer round trips, including the new options and state handling. - **Middle (~40%–60%)**: Moves to HTTP, showing how the request/response model sits on TCP, how connections are managed, and where performance and correctness issues arise. - **Late (~60%–80%)**: Covers NNTP, the news transfer protocol, as a second application-layer case study with different traffic patterns and connection semantics. - **Ending (~80%–100%)**: Treats the UNIX domain protocols—the local, non-network IPC family—contrasting them with Internet-domain sockets and showing where they fit in real implementations. 【Key Takeaways】 - **T/TCP targets the cost of short-lived connections** (Early): the volume's central thread is that ordinary TCP is wasteful for brief request/response exchanges, and T/TCP exists to cut handshake and teardown overhead. This matters because it explains why the protocol extensions look the way they do. - **Protocol behavior is best learned from real traces and implementations** (Early): consistent with the Illustrated series' visual, teach-by-example approach, the material ties abstract protocol rules to observable behavior rather than presenting them in isolation. - **HTTP is a case study in layering** (Middle): the book treats HTTP as an application protocol whose performance and semantics depend heavily on the underlying TCP connection strategy, not as a standalone topic. - **NNTP shows a different application profile** (Late): news transfer has its own connection and transfer patterns, useful for seeing how application requirements shape protocol use. - **UNIX domain protocols are a distinct IPC family** (Ending): local sockets share the socket API but not the network stack, and understanding the contrast clarifies what is genuinely "Internet" about Internet protocols. - **The series assumes prior TCP/IP grounding** (Early): this volume builds on earlier material rather than re-teaching fundamentals, so readers without that base will find it steep. - **Implementation detail is the point** (Middle): the value is in understanding how protocols are actually built and behave, which is what separates this from a configuration guide. 【Reading Tips】 - Read the T/TCP opening carefully; it is the conceptual key to the rest of the volume. Skim if you already know standard TCP handshake and TIME_WAIT behavior well. - Treat HTTP and NNTP chapters as applied case studies—read for how each protocol uses TCP, not as exhaustive protocol references. - The UNIX domain protocols section is short and self-contained; read it last and use it to sharpen your mental model of what the network stack adds. - Keep the earlier volumes nearby. This book assumes you already know TCP/IP fundamentals and will not pause to re-explain them. - Note the OCR warning in the source: use a cleaned DJVU version if available, since text quality affects readability of the technical detail. 【Coverage Limits】 The available excerpts are limited to front-matter and series description; they do not cover specific chapter contents, figures, or code examples, so this guide describes the book's scope and structure rather than its detailed arguments.