This article explains the fundamental differences between long-lived and short-lived network connections, covering their operation processes, resource consumption, typical use cases, and impact on stability and fault tolerance, helping developers choose the right approach for their applications.
This article explains TCP connection basics, the three‑way handshake and four‑way termination, compares short and long connections, discusses keep‑alive mechanisms, and outlines when to use each approach in network and HTTP communication.
TCP connections can be either short-lived, closing after a single request‑response cycle, or long-lived, staying open for multiple exchanges; this article explains their handshake processes, advantages, drawbacks, typical use cases, reasons long connections drop, and practical strategies such as keepalive and reconnection to maintain reliability.
This article explains the fundamentals of TCP connections, detailing the three‑way handshake, four‑step termination, the differences between short‑lived and persistent (long) connections, their advantages, keep‑alive mechanisms, and practical guidelines for choosing the appropriate connection type in various network scenarios.
This article explains HTTP’s key characteristics, compares short‑lived and persistent connections, and explores related concepts such as head‑of‑line blocking, concurrency, and domain sharding, providing readers with a comprehensive understanding of how HTTP manages connections and performance.
This article explains the core characteristics of the HTTP protocol—including its flexibility, reliability, application‑layer nature, request‑response model, and statelessness—and then details short and long connection management, related header fields, head‑of‑line blocking, and practical performance‑enhancing techniques such as concurrent connections and domain sharding.
This article explains HTTP's core characteristics—flexibility, reliability, application‑layer nature, request‑response model, and statelessness—then dives into short‑ and long‑connection management, head‑of‑line blocking, and practical optimization techniques such as concurrent connections and domain sharding.
Meituan‑Dianping’s high‑availability mobile network optimization combines short‑connection tactics—domain merging and IP‑direct selection—to cut DNS lookups, with a proxy‑long‑link architecture (CIP and Tencent WNS) that provides DNS‑independent, multiplexed TCP links, improving latency, success rates, and offering fallback mechanisms for robust app performance.
This article explains how to assess the maximum concurrent user capacity of short‑connection server implementations by using the HTTP Transaction Rate metric, contrasting it with long‑connection testing, and provides practical calculation examples and terminology definitions.
This article explains how HTTP relies on TCP/IP, clarifies the stateless nature of HTTP, and compares long and short connections—including their TCP handshakes, keep‑alive mechanisms, advantages, disadvantages, and appropriate usage scenarios for web and database communications.
This article explains how HTTP relies on TCP/IP, clarifies the stateless nature of HTTP, and compares long‑lasting persistent connections with short‑lived ones, covering their handshakes, advantages, disadvantages, and appropriate usage scenarios.
This article explains how HTTP relies on TCP/IP, clarifies the stateless nature of HTTP, compares short and long connections in HTTP/1.0 and HTTP/1.1, and discusses the advantages, disadvantages, and appropriate use cases for each connection type.
This article explains the differences between long and short TCP/IP connections, outlines three major communication models (server/client, connection type, and send/receive mode), describes synchronous and asynchronous transmission, and reviews various message formats and read/write strategies to help developers design robust network programs.
