Expand description
Patch frames and their encodings.
§4.4 specifies a compact, field-tagged binary encoding for Beck↔Beck traffic. The thin client
is a browser: JSON costs it zero bytes of decoder, and the decoder is the scarce resource in a
10 KB budget. Phase 0 therefore ships JSON on the wire and keeps the binary encoding alongside
it so the trade is a measured number rather than an opinion — beck-p0-bench payload reports
both, and Phase 1 can move the client to binary knowing exactly what it buys.
Every frame carries the seq it brings the subscriber up to. That single field is what makes
(subscription, seq) resumption and, later, optimistic reconciliation cheap (§4.4, §3.7).
Structs§
Enums§
Type Aliases§
- SubId
- A subscription id — content-independent, minted by the client, stable across reconnects.