This article walks through building a Netty‑based WebSocket server integrated with Spring Boot, configuring the channel pipeline, implementing custom handlers, exposing a push‑message service, and testing the end‑to‑end flow that enables the backend to push real‑time messages to web clients.
This article examines three server‑to‑client push techniques—polling, WebSocket, and Server‑Sent Events (SSE)—by detailing their mechanisms, listing concrete drawbacks and advantages, comparing them side‑by‑side, and providing step‑by‑step Node.js demos for real‑time dashboards and chat scenarios.
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 guide explains how to implement reliable scheduled tasks in Chrome extensions under Manifest V3, covering the shift from persistent background scripts to service workers, three practical approaches—including chrome.alarms, content script timers, and event‑driven simulations—plus best‑practice tips for idempotency, logging, and state persistence.
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 why traditional HTTP cannot let servers initiate messages, compares periodic HTTP polling and long polling as workarounds, and introduces the full‑duplex WebSocket protocol—including its handshake, frame format, and typical use cases such as web games and real‑time chat.
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.
HTTP/2 introduces a binary framing layer, multiplexed streams, header compression, and server push, replacing the limitations of HTTP/1.x by enabling a single TCP connection to carry multiple concurrent requests, reducing latency, improving bandwidth usage, and simplifying web development, while also presenting new debugging challenges.
This article explains the shortcomings of HTTP/1.x, introduces the key innovations of HTTP/2 such as binary framing, multiplexing, server push, header compression, request priority, stream reset and flow control, and shows why mastering these concepts is essential for modern web development and interview preparation.
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.
HTTP/2, the first major update to HTTP since 1.1, introduces binary framing, multiplexing, server push, and header compression, dramatically improving web performance by reducing latency, consolidating connections, and optimizing resource delivery, as detailed in this comprehensive overview.
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 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 HTTP/2 fundamentals, showcases its adoption by major Chinese sites, and provides a step‑by‑step Node.js tutorial—including installation, SSL setup, server code, and a demo that fires 100 parallel requests—to help developers experience the protocol’s benefits.
HTTP/2 replaces the text‑based HTTP/1.x with a binary, multiplexed protocol that reduces latency, eliminates head‑of‑line blocking, compresses headers, enables server push, and improves security, offering REST APIs faster, more efficient communication while preserving familiar semantics for developers.
This article compares HTTP/2 with its predecessor HTTP/1.x, detailing performance gains through multiplexing, binary framing, header compression, and server push, and explains the underlying mechanisms such as TCP behavior, binary frames, static and dynamic header tables, illustrating concepts with visual examples.
HTTP/2 introduced server push to let servers proactively send resources, but it suffers from issues such as cache invalidation after connection closure, difficulty identifying needed pages, lack of authentication reuse, and other pitfalls, so understanding its traps and best practices is essential for effective use.
HTTP/2, the modern successor to HTTP/1.1, introduces binary framing, header compression, multiplexing, server push, and other enhancements that dramatically reduce latency and improve efficiency, making web pages load faster and more reliably across browsers and servers that support the protocol.
This article examines how widespread HTTP/2 adoption changes front‑end architecture, demonstrates concrete speed improvements through multiplexing, priority, and server‑push with real‑world demos and HAR analysis, and explains which legacy optimizations become obsolete.
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 guide explains how HTTP/2 changes traditional front‑end performance tricks, covers browser support, TLS requirements, Server Push benefits, and provides a concise Nginx configuration example to enable HTTP/2 on your site.
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 how HTTP/2 replaces SPDY, introduces multiplexing, header compression and Server Push, and shows why many HTTP/1 optimization tricks become obsolete while still offering practical strategies for faster resource loading on modern web pages.
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.
