DHMP LIVE DEMO

Send only what changed.

A 160×90 logical framebuffer is updated as independent fixed-size DHMP records. The receiver keeps every old pixel until a newer value for that pixel arrives.

connecting… 0 source FPS 0 pixel updates/s 0% of full frames sent 0 DHMP record KB/s

Source

generated locally

Receiver

only received pixels are changed

Latest semantics

Each changed pixel becomes one 16-byte application record and is processed through DHMP Latest. No frame reconstruction is required.

Persistent framebuffer

No update means no change. The receiver leaves the previous pixel on screen until a newer update arrives.

What this proves

This page demonstrates DHMP record/state semantics in the deployed backend. Browser control traffic uses ordinary HTTPS POSTs; browsers cannot send raw DHMP IPv6 packets.