The article analyzes why HTTP/3, built on QUIC over UDP, can outperform HTTP/2 in lossy or mobile networks by eliminating TCP's head‑of‑line blocking, offering faster handshakes, seamless connection migration, and better congestion control, while also outlining scenarios where HTTP/2 remains preferable.
The article examines how IPv6 was designed to eliminate decades‑old networking baggage, but its reliance on discarding legacy layers, MAC addresses, ARP, and DHCP makes the ideal blueprint unattainable in today’s mixed‑technology Internet.
This article examines how HTTP/3’s Connection ID decouples a connection from its IP/port tuple, enabling transparent network migration for gRPC over QUIC, and explores the practical limits of 0‑RTT, stream‑level flow control, and real‑world adoption strategies.
This article details how the Vivo Game Center team tackled slow page loads and resource failures in weak‑network environments by integrating the QUIC‑enabled Cronet library into OkHttp, defining precise network states, using custom interceptors, and conducting A/B tests that reduced failure rates by 40% and cut request latency by 7%.
This article traces the evolution from HTTP/1.1 to HTTP/3, explains how QUIC leverages UDP to achieve faster, secure connections, and details its handshake, connection migration, head‑of‑line blocking solutions, congestion and flow control mechanisms.
Despite widespread browser and CDN support for HTTP/3, most developers still struggle to deploy it end‑to‑end because of missing QUIC implementations in language runtimes, fragmented open‑source tooling, and compatibility issues with core libraries like OpenSSL.
The Go core team’s experimental HTTP/3 proposal, first introduced in 2024, has been postponed despite years of community demand, highlighting challenges in API design, backward compatibility, resource allocation, and the practical dominance of HTTP/2 over the newer protocol.
This article explains how Java 24 and OpenJDK introduce HTTP/3 via JEP 517, describes the QUIC protocol that powers it, compares performance against HTTP/2, and provides Java benchmark code showing reduced latency and fewer TCP connections when using HTTP/3.
This article explains how Java 24 and OpenJDK add HTTP/3 support, compares its speed to HTTP/2 using benchmark code, and shows why the QUIC‑based protocol delivers lower latency and fewer TCP connections for modern web applications.
Samba 4.23 introduces QUIC transport for SMB3, enables Unix extensions by default, adds Prometheus‑compatible monitoring, improves file timestamp handling, and provides new backup options, while the article also offers step‑by‑step Ubuntu installation commands.
The Go core team proposes an experimental HTTP/3 implementation in the x/net/http3 package, outlining its background, development stages, sample code, and the potential benefits for compatibility, stability, and performance in backend networking.
This article demonstrates how to build high‑performance, low‑latency Go microservices by integrating gRPC with HTTP/3 over QUIC, covering server and client implementations, a sample Analyze service, step‑by‑step communication flow, and performance comparisons against traditional HTTP/2‑based gRPC.
This article traces the evolution from HTTP/1.1 to HTTP/3, explains QUIC's design and its advantages over TCP, and examines how features like connection migration, head‑of‑line blocking elimination, congestion control, and flow control improve latency and reliability for modern web applications.
ROFF is a Rust‑implemented, seven‑layer gateway that delivers high‑throughput load balancing with memory‑safe performance, TLS hardware offload, native QUIC/HTTP3 support, a hot‑reload/upgrade mechanism, and an extensible module system allowing over thirty built‑in filters and custom Rust macros.
The article provides a comprehensive technical overview of HTTP's history, the design and advantages of the QUIC protocol—including connection establishment, migration, head‑of‑line blocking mitigation, congestion control, ACK handling, and stream/connection flow control—while contrasting it with TCP and HTTP/2 mechanisms.
This article summarizes the ACM MM 2024 paper on AutoRec, a timeliness‑enhanced loss‑recovery mechanism for large‑scale live streaming that leverages on‑off mode adaptation, online learning, and injection control to cut video stall frequency by 11.4% and duration by 5.2% without client changes.
The paper “Toward Timeliness‑Enhanced Loss Recovery for Large‑Scale Live Streaming” introduces AutoRec, an on‑off‑mode‑aware packet‑loss recovery mechanism implemented on QUIC that reduces average stall frequency by 11.4% and duration by 5.2% without client‑side changes, and validates its effectiveness in both test‑bed and real‑world CDN deployments.
This article explains WebTransport, an HTTP/3‑based API that offers multiplexing, flow control, and end‑to‑end encryption, compares it with WebSocket, and provides real‑world use cases such as cloud gaming and low‑latency live streaming with code examples.
This article reviews the evolution of HTTP from its early versions to HTTP/3, explains the QUIC protocol and its advantages over TCP, and discusses connection establishment, migration, head‑of‑line blocking, congestion control, and flow control mechanisms that improve modern web performance.
This article traces the evolution of HTTP from its 1991 origins through HTTP/2 and HTTP/3, explains how QUIC leverages UDP to reduce latency, and details QUIC's connection establishment, migration, head‑of‑line blocking mitigation, congestion control, and flow‑control mechanisms.
This article traces the evolution of HTTP from its 1991 inception through HTTP/1.1, HTTP/2, and HTTP/3, explains the QUIC protocol’s design and advantages, and details connection establishment, congestion control, flow control, and head‑of‑line blocking mitigation techniques used in modern web transport.
This article traces the evolution from HTTP/1.1 to HTTP/3, explains how QUIC built on UDP to reduce connection latency, avoid head‑of‑line blocking, support seamless connection migration, and introduce advanced congestion and flow‑control mechanisms that give HTTP/3 a performance edge over its predecessors.
The team built a reusable low‑latency live‑streaming platform for the European Cup that replaces HLS with RTMP over QUIC, reuses VOD bandwidth, automates stream control, and cuts playback latency by 20 seconds while dramatically lowering bandwidth costs and delivering stable 1080p 50 fps HDR video.
This article details the deployment of QUIC in Trip.com’s mobile app, covering multi‑process architecture, containerized upgrades, service discovery, health monitoring, push‑pull resilience, full‑link tracing, congestion‑control algorithm redesign, and the resulting performance and reliability improvements achieved across global users.
This article explains the evolution of HTTP from 1.1 to HTTP/3, introduces the QUIC protocol and its packet‑based design, and details how QUIC reduces RTT, solves head‑of‑line blocking, improves congestion and flow control, and supports connection migration.
This article explains how QUIC, a UDP‑based transport protocol developed by Google, overcomes TCP's limitations such as handshake latency and head‑of‑line blocking, offering lower latency, multiplexing, built‑in TLS 1.3 security, and why it powers the emerging HTTP/3 standard.
This article explains the evolution from HTTP/1.1 to HTTP/3, detailing QUIC's UDP‑based design, its impact on connection establishment, migration, head‑of‑line blocking, multiplexing, congestion control, forward error correction, and flow‑control mechanisms for modern web services.
This article explains the evolution from HTTP/1.1 to HTTP/3, detailing QUIC’s UDP‑based design, its 1‑RTT handshake, connection migration, head‑of‑line blocking elimination, congestion‑control enhancements, forward error correction, and stream‑ and connection‑level flow control.
The article recounts a Tencent engineer's six‑year journey from early DNS‑bypass tricks to modern HTTP/2 + QUIC implementations, highlighting technical challenges, security innovations, and the iterative process behind multiple promotion evaluations.
QDSR is a high‑performance QUIC traffic‑forwarding framework that integrates Direct Server Return to remove redundant downstream forwarding in layer‑7 load balancers, allowing multiple real servers to stream data directly to clients via a one‑way tunnel, achieving up to 12.2× higher throughput and significantly lower latency while preserving security and connection consistency.
BiliBili created the proprietary BMT (Bili Media Transport) streaming protocol, which consolidates FLV and HLS delivery into a low‑overhead, multi‑track, codec‑agnostic format using QUIC‑accelerated back‑haul, cutting daily CDN back‑haul traffic by over 100 GB and enabling richer live‑streaming features.
Tencent’s newly open‑sourced TQUIC, a high‑performance, lightweight, cross‑platform QUIC library written in Rust, offers fast transmission, high performance, extensive congestion‑control algorithms, multi‑path support, and strong security, and has already boosted core services such as video, advertising, gaming, and cloud CDN, demonstrating its broad scenario value and robust architecture.
Tencent has open‑sourced TQUIC, a Rust‑based, high‑performance, lightweight cross‑platform QUIC library that supports multiple congestion‑control algorithms, multi‑path networking, and memory‑safe operation, delivering 2‑30% faster transmission and up to 20% higher processing speed while improving latency‑sensitive services such as video, gaming, advertising, and e‑commerce.
This article details the motivation, architecture, and step‑by‑step integration of Google’s Cronet network library into NetEase Cloud Music’s Android client, covering adaptation layers, interceptor handling, timeout support, compatibility fixes, performance gains, and future QUIC enhancements.
Taobao migrated its long‑chain network from a private SlightSSL over HTTP/2 to a full HTTP3/QUIC stack built on the XQUIC library, adding unified TNET interfaces, UDP probing and fallback, which cut recommendation latency by up to 33 %, transaction latency 32 %, boosted upload speed 21 % and short‑video download 18 % while solving UDP port, load‑balancing and kernel memory challenges.
This article explains the key differences and performance trade‑offs among HTTP/1.1, HTTP/2, and HTTP/3, detailing keep‑alive, pipelining, streams, multiplexing, QUIC’s 0‑RTT handshake, connection migration, congestion and flow control, and provides practical guidance on when to adopt each protocol.
This article traces the evolution of service mesh from its early concepts through microservice 1.0 and 2.0, analyzes the shortcomings of Envoy‑based sidecars, and explores future directions such as Go‑based data planes, WASM plugins, eBPF/VPP acceleration, QUIC transport, and on‑demand xDS delivery.
This article details the background, design choices, and concrete implementation of integrating the QUIC protocol into both client and server components, describing multi‑channel management, load balancing, performance gains, and future optimization plans for improving network reliability in diverse overseas environments.
By replacing TCP+TLS with QUIC, Tencent Meeting cuts connection‑setup latency by nearly half, enables seamless Wi‑Fi‑to‑cellular handover through connection migration, improves login success, tolerates high packet loss, and incorporates fallback and crash‑guard mechanisms to ensure reliable video conferencing.
The Vivo Internet Operations team outlines how they cut short‑video startup latency by warming DNS caches, consolidating domains for HTTP/1.1 reuse, deploying HTTP/2 and QUIC, and optimizing CDN edge placement, achieving up to 30 ms DNS gains, 40 ms image load reductions, and lower request and first‑byte latencies.
The article explains how HTTP/3 abandons TCP in favor of the QUIC protocol built on UDP, detailing TCP's head‑of‑line blocking, handshake latency, middlebox rigidity, and how QUIC’s reliability, multiplexing, and fast handshakes address these issues while also noting deployment challenges.
Taobao’s network team details the evolution from proprietary Slight SSL to HTTP3/QUIC via the XQUIC library, describing TNET capabilities, deployment challenges, and performance gains across shopping, transaction, upload and video scenarios, and the extensive optimizations—such as UDP probing, 0‑RTT increase, and packet handling—that delivered measurable latency reductions and higher success rates.
Bilibili’s video CDN replaced its traditional TCP‑based gateway with a QUIC/HTTP‑3 gateway and, to curb the extra CPU load caused by complex UDP handling, adopted AF_XDP kernel‑bypass sockets that redirect packets via XDP, cutting CPU usage by about half, raising peak bandwidth to roughly 9 Gbps and improving per‑bandwidth efficiency by up to 30 %.
This article explains the fundamentals of HTTP, how browsers build and send requests, the structure of request and response messages, and the performance improvements introduced by HTTP 2.0 and the QUIC protocol built on UDP.
This article explains the fundamentals of the HTTP protocol, covering request preparation, message structure, methods, headers, caching, the request/response cycle, HTTP/2 enhancements, and the QUIC protocol's advanced features for faster, more reliable web communication.
This article explains how HTTP/3, built on the QUIC transport, improves latency, reliability, and security compared to earlier HTTP versions, outlines its adoption across browsers and CDNs, and lists language libraries for developers to start implementing the new protocol.
This article explains the evolution of HTTP from 1.1 to HTTP/3, how QUIC leverages UDP and TLS to achieve low‑latency 0‑RTT connections, solves head‑of‑line blocking, improves congestion and flow control, and why these advances matter for modern web applications.
This article explains how QUIC implements reliable transmission on top of UDP by using monotonic packet numbers, stream IDs and offsets, independent flow‑control windows, and integrated TLS, thereby eliminating TCP’s retransmission ambiguity, head‑of‑line blocking, and improving congestion control and connection migration.
To achieve sub‑second start‑up for mobile video streaming, the iQIYI overseas project applies layered HTTPS optimizations—including DNS and certificate caching, ECDHE/X25519 key exchange, false start, lightweight cipher suites, ECDSA certificates, OCSP stapling, and session‑ID/ticket reuse—while transitioning toward TLS 1.3 0‑RTT and HTTP/3 QUIC for further latency reduction.
This article explains the evolution from HTTP/1.1 to HTTP/3, highlights the limitations of HTTP/2 such as head‑of‑line blocking and TCP‑based latency, and shows how QUIC’s UDP‑based design, 0‑RTT handshakes, connection migration, and advanced congestion‑control mechanisms overcome those challenges to deliver faster, more reliable web traffic.
The article explains how TCP, the long‑standing transport for HTTP/1.x and HTTP/2, suffers from head‑of‑line blocking and handshake latency, why protocol ossification hinders upgrades, and how HTTP/3’s QUIC built on UDP overcomes these issues while introducing its own deployment challenges.
This article explains the recent standardization of HTTP/3, Alibaba's XQUIC implementation, optimal scenarios for QUIC, its user‑space transport advantages, performance gains in mobile e‑commerce, and practical solutions for high‑performance UDP handling on the server side.
QUIC replaces TCP when long, lossy or wireless‑induced jitter dominates, offering multi‑stream, 0‑RTT, user‑space transport; Alibaba’s XQUIC library demonstrates 15‑20% latency cuts, 26% throughput gains via XDP‑based UDP bypass, and outlines a four‑stage adoption path from business value to open‑source leadership.
This article explains the evolution of HTTP, the release of the HTTP/3 RFC, how QUIC leverages UDP to provide faster, secure connections with 0‑RTT handshakes, solves head‑of‑line blocking, improves congestion and flow control, and details its core mechanisms such as connection migration and ACK handling.
The article explains how HTTP/3, standardized as RFC 9114 after five years of work, replaces TCP with the UDP‑based QUIC protocol to overcome HTTP/1.1 and HTTP/2 limitations such as head‑of‑line blocking, improving multiplexing, congestion control, and security.
This article explains the significance of HTTP/3 for web performance, outlines its standardization history, compares it with HTTP/1.1 and HTTP/2, presents benchmark results, and discusses practical adoption considerations such as QUIC, 0‑RTT, and current implementation support.
This article examines the inherent shortcomings of the TCP protocol, including the difficulty of upgrading the stack, the latency introduced by its three‑way handshake and TLS, head‑of‑line blocking caused by packet loss, and the high cost of connection migration when network conditions change.
This article explains how NetEase Cloud Communication leverages the QUIC protocol—detailing its transport‑layer advantages over TCP, protocol‑level differences, and specific optimization practices such as multiplexing, unreliable DATAGRAM frames, compression, and dynamic redundancy—to dramatically improve audio‑video signaling latency, loss tolerance, and bandwidth utilization in challenging network conditions.
The XQUIC project, Alibaba’s high‑performance open‑source QUIC transport library that powers mobile Taobao and large‑scale gateway services with up to 20 % latency reduction, offers a standards‑compliant stack (QUIC‑Transport, QUIC‑TLS, HTTP/3, qlog) and multi‑path XLINK, and invites students in the Open Source Summer program to extend the code, improve diagnostics, and earn mentorship and rewards.
The article details how Trip.com introduced and customized QUIC in its mobile app to overcome long‑distance, unstable overseas connections, achieving a 20% latency reduction and 99.5% success rate through client‑side Cronet trimming, IP direct‑connect, multi‑link support, 0‑RTT, connection migration, QPACK tuning, and adaptive TCP/QUIC selection.
This article presents a comprehensive optimization of video caching on iOS, detailing background analysis, a dynamic concurrency design based on network conditions and device performance, test results showing up to 2.5‑fold speed gains, and the core implementation code.
This article describes how Trip.com’s backend engineers introduced QUIC to the Trip.com App, redesigned the Nginx‑based server architecture for multi‑process deployment, solved connection‑migration challenges with a custom load‑balancing layer, and enabled 0‑RTT support using shared ticket keys, achieving roughly a 20% reduction in request latency.
Alibaba’s collaboration with Chinese academia led to the approval of the GRTN low‑latency multimedia transmission standard and the open‑source release of its multi‑path QUIC library XQUIC, which together cut video stall rates by over 60%, boost throughput, shorten download times, and are now powering live streaming, video conferencing, e‑commerce and cloud‑gaming services across Alibaba’s ecosystem.
The authors upgraded the Mahimahi record‑and‑replay framework by replacing Apache with modular Nginx, adding native HTTP/2 support and integrating a QUIC module (via quiche), enabling replay of captured traffic under modern protocols, precise network condition control and open‑sourcing the extensions for reproducible performance experiments.
The article examines the limitations of TCP and HTTP/2, explains how Google's UDP‑based QUIC protocol addresses issues such as head‑of‑line blocking, connection migration, and RTT estimation, and compares performance in both good and poor network conditions, highlighting its multiplexing, flow‑control, and security advantages.
The article reviews Chrome's 2021 updates—including version releases, the removal of Flash, major WebAssembly enhancements, the QUIC protocol, and the upcoming WebGPU—while also highlighting broader front‑end ecosystem news such as Vercel, Figma, and Rust, illustrating how these advances shape modern web development.
XQUIC is Alibaba's open‑source, standards‑compliant QUIC implementation that delivers lightweight binaries, high‑performance transport, and cross‑platform support, enabling faster, more reliable data transfer for mobile apps and cloud services while fostering community collaboration through open source.
Chrome 97, released on January 4, 2022, introduces 14 new features—including the groundbreaking WebTransport protocol powered by QUIC for low‑latency bidirectional communication, updates to DevTools such as the Recorder for user‑flow testing, and a suite of enhancements that signal a rapid evolution of web technologies.
This article explains the evolution of HTTP, compares HTTP/1.1, HTTP/2, and HTTP/3, and presents benchmark results from three global data centers showing how HTTP/3’s QUIC‑based multiplexing and 0‑RTT dramatically reduce page load latency.
This article traces the evolution of HTTP from its early TCP‑based origins through HTTP/1.0, 1.1, SPDY, HTTP/2, and finally to HTTP/3, explaining how QUIC over UDP addresses latency, head‑of‑line blocking, and security challenges of previous versions.
Tencent’s sTGW team introduced the TQUIC protocol stack, a lightweight QUIC/HTTP‑3 implementation with 0‑RTT handshakes, connection migration, and real‑time frames, cutting user login latency by 30 % and raising 500 ms download success from 60 % to 90 % in weak‑network conditions while shrinking the Android library to roughly 3 MB.
Tencent’s sTGW team built the TQUIC protocol stack, leveraging QUIC/HTTP3 to cut login latency by 30% and achieve 90% request success within 500 ms on weak networks, and the article details its architecture, core advantages, implementation challenges, and real‑world performance gains across multiple services.
This article traces the evolution of HTTP from its earliest version through HTTP/2, explains the limitations of each iteration, and demonstrates how QUIC's UDP‑based design, 0‑RTT connections, connection migration, and flexible congestion control overcome those issues to become the next‑generation web transport protocol.
Since 2015, Ant Group’s Alipay client and gateway teams have been deploying QUIC, the next‑generation transport for HTTP/3, across mobile payment and overseas acceleration scenarios, detailing background, design choices, deployment frameworks, key technologies like connection migration, 0‑RTT, lossless upgrades, and related patents.
This article explains how QUIC solves TCP's head‑of‑line blocking, reduces connection‑setup overhead, enables seamless connection migration, lowers retransmission probability, and improves congestion control, offering a more efficient alternative to TCP for modern network environments.
This article traces the development of the HTTP protocol from its earliest 0.9 version through HTTP/1.1, HTTP/2, and finally HTTP/3 built on QUIC, highlighting how each iteration improved speed, efficiency, and mitigated head‑of‑line blocking while introducing new challenges.
This article reviews Google’s pioneering SPDY protocol, its key features and impact on HTTP/2, then explores the disruptive QUIC protocol built on UDP, detailing its connection setup, Diffie‑Hellman encryption, multiplexing, connection migration, and other enhancements that boost web performance.
QUIC, a UDP‑based transport protocol that merges TCP reliability, UDP speed, and TLS security, underpins HTTP/3 by eliminating TCP’s three‑way handshake and head‑of‑line blocking, offering connection migration, 0‑RTT latency, customizable congestion control, fully encrypted packets, and is already being deployed in services such as Tencent Cloud CDN.
This article explains how NetEase Cloud's audio‑video service overcomes the limitations of TCP in poor network conditions by adopting a QUIC‑based acceleration proxy architecture, detailing its design, key optimizations, and performance gains in latency, packet loss resistance, and bandwidth utilization.
This article reviews the evolution of HTTP from version 1.1 to HTTP/2 and HTTP/3, explaining key features such as persistent connections, pipelining, binary framing, header compression, multiplexing, and QUIC's advantages, while also highlighting the remaining drawbacks like head‑of‑line blocking, TCP connection limits, and security concerns.
This article traces the evolution of the HTTP protocol from its early days through HTTP/1.0, 1.1, SPDY, HTTP/2, and finally to HTTP/3, explaining how QUIC over UDP addresses TCP's latency and security limitations while also highlighting remaining challenges.
This article traces the evolution of HTTP from its 1991 origins through HTTP/1.0, 1.1, SPDY, and HTTP/2, explaining why the shift to UDP‑based QUIC in HTTP/3 promises faster, more secure web delivery while also highlighting the new protocol’s challenges.
This article reviews the pioneering SPDY protocol that inspired HTTP/2, then delves into Google's disruptive QUIC protocol—explaining its UDP foundation, Diffie‑Hellman encryption, connection migration, and advanced features that overcome TCP limitations, while comparing their roles in modern web communication.
This article reviews the development and core features of HTTP/2, explains why its TCP‑based design still suffers from head‑of‑line blocking and handshake latency, and argues that these inherent limitations make the transition to HTTP/3 over QUIC inevitable for modern web developers.
This article reviews the evolution of web communication protocols, detailing SPDY's pioneering features that influenced HTTP/2 and exploring QUIC's disruptive UDP‑based design, security mechanisms, multiplexing, connection migration, and other enhancements that reshape modern internet performance.
This article traces the evolution of HTTP from its 1991 origins through HTTP/1.0, 1.1, HTTP/2, and finally HTTP/3, explaining how QUIC over UDP addresses TCP’s latency and security limitations while also highlighting remaining challenges.
This article reviews October's key tech updates, covering NPM v7's new workspace and peer‑dependency features, Chrome's rollout of HTTP/3 over QUIC, Webpack 5's Module Federation for JavaScript architecture, the physics behind iOS UIScrollView animations, Chinese web‑font handling, the lightweight SVGA animation format, and a 1 KB JavaScript 3D game demo.
Youku’s Playback Center tackles common video issues by combining real‑time data‑driven tuning, adaptive‑bitrate streaming, QUIC‑based transport optimization, device‑specific capability management, and post‑decoding enhancements, all supported by a tiered CDN and multi‑layer metric system that together ensure smooth, high‑quality playback across diverse networks and devices.
This article explains the fundamentals of HTTP, the differences between GET and POST, common status codes, HTTPS and TLS handshakes, the improvements introduced by HTTP/2 such as binary framing, multiplexing and header compression, as well as the role of QUIC and DNS in the end‑to‑end web request flow.
This article explains the evolution from HTTP/1.1 to HTTP/3, detailing QUIC's design, zero‑RTT connections, connection migration, head‑of‑line blocking elimination, multiplexing, congestion and flow control improvements, and why HTTP/3 is poised to become the next‑generation web protocol.
Microsoft announced on its official tech blog that it has open‑sourced MsQuic, its internal cross‑platform implementation of the experimental QUIC transport protocol, which underpins HTTP/3 and is already integrated into Windows, Microsoft 365, .NET Core, and SMB, offering performance and security improvements.
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.
