This article traces the evolution of HTTP from its early versions to HTTP/2 and QUIC, explains the shortcomings of HTTP/1.1 such as head‑of‑line blocking and lack of encryption, details the performance‑boosting features of SPDY, HTTP/2 and QUIC, and discusses the remaining challenges like connection latency, server load, and NAT traversal.
This article explains what QUIC is, outlines HTTP/3’s advantages over HTTP/2, and provides step‑by‑step instructions with code samples for compiling Node.js’s QUIC implementation and running a simple QUIC server and client to observe protocol behavior.
The article explains Baidu App’s weak‑network optimization strategy, detailing metrics such as httprtt, tcprtt, throughput and signal strength, describing active probing and passive collection for detection, defining thresholds, and outlining best‑practice techniques like QUIC activation, pre‑connection and composite connections that markedly improve success rates and reduce latency.
Tencent Cloud’s overseas video live‑streaming architecture combines tiered carrier procurement across North America, APAC and Europe, decentralized origin servers with dual‑active synchronization, and network optimizations such as DNS‑based scheduling, QUIC and QTCP, cutting stutter rates while tightly controlling costs.
Upcoming IETF discussions aim to replace the long‑standing TCP‑based HTTP with a new UDP‑based protocol, QUIC, rebranded as HTTP/3, offering lower latency and improved security, while distinguishing Google’s gQUIC from the IETF’s iQUIC and gaining industry support.
This article explains how the protocol formerly known as HTTP-over-QUIC was officially renamed to HTTP/3, outlines the role of the IETF QUIC working group, the distinction between iQUIC and gQUIC, and highlights key interoperability milestones and resources.
IMWebConf 2018 gathered nearly 500 on‑site attendees and over a thousand online viewers for a deep dive into front‑end standards, WebXR, QUIC, WePY, mpvue, fast‑app, cross‑platform frameworks like Weex and Taro, Node.js performance, and cutting‑edge data visualization techniques.
The article summarizes four technical sessions covering cloud‑based AI applications, progressive web apps with service‑worker and manifest details, WebAssembly performance advantages for native‑like web development, and the practical use of QUIC to reduce latency in network communication.
This article explains what head‑of‑line blocking is in HTTP, why HTTP/1.1 suffers from it, how HTTP/2 over TCP mitigates request‑level blocking but not transport‑level issues, and how QUIC over UDP fully resolves the problem.
This article introduces the QUIC transport protocol, explains its design goals and key features, details a practical iOS implementation using Chromium and Stellite libraries, presents code examples, and compares QUIC’s download latency against HTTP/2 on Wi‑Fi and 4G networks.
This article reviews the challenges of web performance, analyzes HTTP/1.1, HTTP/2, TLS, and QUIC protocols, discusses optimization techniques such as TCP fast open, TLS false start, server push, preconnect, and presents practical recommendations from the 2017 ArchSummit presentation.
With broadband speeds soaring, UDP’s simplicity and low latency now outperform TCP in web browsing, streaming, gaming, and IoT, as real‑world tests from Akamai and Google show dramatically lower packet loss, faster connections, and reduced buffering, signaling a shift toward UDP‑centric networking.
Ctrip's wireless development team shares a comprehensive overview of their app's network architecture, common performance pitfalls such as DNS and TCP issues, and a series of practical optimizations—including DNS caching, quality detection, priority handling, retransmission, payload reduction, and protocol upgrades—that dramatically improved service success rates and reduced latency.