1 views collected around this technical thread.
This article explains the three common server‑to‑client push techniques—polling, WebSocket, and SSE—detailing their principles, advantages, and drawbacks, then provides a step‑by‑step Node/Express and plain‑HTML demo showing how to create and use an SSE connection.
This tutorial compares server‑push techniques—polling, WebSocket, and Server‑Sent Events—detailing their mechanisms, advantages, and drawbacks, then walks through setting up a simple SSE demo with Node.js and plain HTML, helping developers pick the right solution for real‑time data scenarios.
This article explains the three main server‑to‑client push techniques—polling, WebSocket, and Server‑Sent Events—detailing their advantages, drawbacks, browser compatibility, and provides step‑by‑step Node.js and front‑end demos for implementing SSE in real‑time applications.
The article compares EventSource and WebSocket, outlining their respective advantages, disadvantages, and appropriate use cases for server‑push versus bidirectional real‑time communication in web applications such as the ChatGPT interface.
This article provides a comprehensive technical analysis of the HTTP/2 protocol, detailing its architectural improvements over HTTP/1.1, including HPACK header compression, binary framing, stream multiplexing, and server push, while demonstrating practical packet capture techniques to illustrate its performance optimizations.
The article thoroughly explains HTTP/2, detailing its optional clear‑text or TLS connection setup, multiplexed frames and streams, HPACK header compression, server‑push mechanism, application‑layer flow control, and the protocol’s lingering challenges such as TLS handshake latency and TCP head‑of‑line blocking that HTTP/3 seeks to resolve.
This article reviews HTTP/2's core features, evaluates its performance advantages and limitations in real‑world web deployments, discusses server‑push and proxy challenges, and offers a forward‑looking perspective on its adoption across the industry.
This article explains the principles, models, and implementations of Comet (including stream‑based and long‑polling approaches) and WebSocket as server‑push techniques for real‑time web applications, comparing their advantages, limitations, and practical deployment considerations.
This article reviews HTTP/2's core features such as binary framing, multiplexing, header compression, and server push, evaluates their performance benefits and real‑world limitations, discusses implementation challenges in Go and proxy servers, and provides references for further study.
This article demonstrates how to add on‑demand and periodic HTTP/2 server‑push functionality in Go, explaining the required handlers, showing complete Go code examples, and detailing the HTTP/2 frame exchange observed with an h2c client.
This article explains HTTP/2’s new features—HPACK header compression using static and dynamic tables with Huffman coding, and Server Push via PUSH_PROMISE frames—detailing how they reduce bandwidth, improve latency, and the underlying stream state machine, illustrated with code snippets and diagrams.
This article explains HTTP/2's header compression using the HPACK format—including static and dynamic tables, Huffman coding, and literal encoding—and the Server Push mechanism with PUSH_PROMISE frames, illustrating how these features reduce bandwidth and improve request latency.
An in‑depth guide walks through HTTP/2 fundamentals—binary framing, streams, messages, and frames—detailing each frame type (DATA, HEADERS, PRIORITY, etc.), Go’s implementation nuances, multiplexing benefits, and practical examples, helping developers harness HTTP/2’s performance gains.
This article demonstrates how to build an HTTP/2 server and client in Go, covering TLS certificate generation, server and client implementations, switching between HTTP/1.1 and HTTP/2, server‑push handling, and full‑duplex echo communication with complete code examples.
Tencent CDN’s implementation of HTTP/2 Server Push predicts and preloads dependent resources via link tags or headers, creates PUSH_PROMISE frames, and streams assets before the main response, yielding measurable latency reductions on real‑world pages when used with proper sizing, priority, and cache awareness, while avoiding slow‑start and buffer issues.
This article explains how HTTP/2 server push works, why it improves page load performance, and provides practical Node‑SPDY code examples for pushing assets, redirects, cache‑validation messages, and integrating Server‑Sent Events to notify clients of pushed resources.
This article explains the Pull mode of Pushlets, detailing its protocol steps, server-side session and queue management, client interactions, key configuration parameters, and the encapsulation of Pushlets into a Channel service for scalable backend message pushing.
This article explains the key innovations of HTTP/2—including binary framing, multiplexing, header compression, request priority, server push, and flow control—while also providing practical tools and experimental results that demonstrate its performance advantages over HTTP/1.1 and SPDY.
This article examines server‑push technologies such as Comet, comparing plugin‑based socket approaches with HTTP long‑connection methods like AJAX long‑polling and iframe/htmlfile streaming, and provides practical guidance on building robust Comet applications using frameworks such as Pushlet.
This article explains the concept of HTTP/2 server push, demonstrates how to implement it using the node‑spdy module with code samples for pushing assets, redirects, and SSE notifications, and discusses practical considerations and future possibilities for optimizing web performance.