How HTTP Streaming Evolved: From Simple Downloads to Adaptive Bitrate

Internet multimedia transmission can be divided into download transfer and streaming transfer, with streaming further split into sequential (Video on Demand) and real‑time (Live Streaming). VOD stores media on a server for client requests, while live streaming delivers content as it is generated.

HTTP‑based streaming has become mainstream due to several advantages: it is firewall‑friendly, lets the client control media access without the server maintaining per‑client sessions, and can run on standard HTTP servers, leveraging CDN support for large‑scale access.

Evolution of HTTP Streaming Technology

The technology has progressed through four major stages:

Full file download before playback.

Progressive download, allowing playback while the file is still downloading, provided metadata is placed at the file start.

Pseudo‑streaming, which adds seek capability to progressive download, enabling users to jump to un‑downloaded portions.

Adaptive bitrate streaming, where multiple bitrate versions of the same video are available and the client dynamically switches based on network conditions.

Adaptive bitrate implementations include Apple’s HTTP Live Streaming (HLS), Adobe’s HTTP Dynamic Streaming (HDS), and the international standard MPEG‑DASH (Dynamic Adaptive Streaming over HTTP).

How a VOD Streaming Server Works

A common setup uses Nginx with its built‑in flv and mp4 modules (ngx_http_flv_module and ngx_http_mp4_module). These modules support progressive seek playback via byte‑range requests. To enable efficient seeking, the server must provide metadata mapping video timestamps to byte offsets, typically stored in the file’s metadata (e.g., FLV metadata or MP4’s moov box).

When a client requests a specific time offset, the server either receives a byte‑range request directly (if the client knows the mapping) or must translate the time offset to a byte offset using the metadata before responding.

Understanding I‑frames (key frames) is crucial: they can be decoded independently, while other frames depend on the nearest preceding I‑frame, which explains why seeking often lands on the nearest I‑frame.

Overall, HTTP‑based streaming leverages standard web infrastructure, firewall compatibility, and CDN optimization to deliver scalable video services.