Skip to main content

Crate moq_binary

Crate moq_binary 

Source
Expand description

Opaque binary payloads over moq-net tracks, in two modes:

  • snapshot: lossy. One value updated over time; a consumer only gets the most recent one. Older values are superseded and dropped.
  • stream: lossless. An ordered append-log of self-contained payloads, delivered in order with nothing superseded. Bounded by the group cache: see stream for what that costs a consumer that falls behind.

Pick snapshot when consumers care about “what is the value now” (a poster image, a serialized state blob) and stream when they care about every payload (an event log, a sequence of samples).

The bytes are opaque: this crate frames them onto a track and optionally compresses them, and never looks inside. For JSON documents reach for moq-json instead, which adds RFC 7396 merge-patch deltas on top of the same two modes.

Compression is moq-flate, the same group-scoped DEFLATE moq-json uses, so the two agree on the wire: each group is one raw DEFLATE stream, sync-flushed at every frame boundary. A stream therefore compresses each payload against the earlier ones in its group, while a snapshot group holds a single self-contained value.

Modules§

snapshot
Lossy latest-value binary publishing over moq-net tracks.
stream
Lossless append-log binary publishing over moq-net tracks.

Enums§

Compression
How a binary track compresses its frames.
Error
Errors produced while publishing or consuming binary payloads.

Type Aliases§

Result
A Result using this crate’s Error.