Output Bytes HTTP

1 VersionOutput

Forwards each Bytes value verbatim over independent egress channels — a binary WebSocket broadcast and/or async HTTP POST as application/octet-stream — so raw binary blobs from an upstream encoder reach live clients or an external endpoint.

How it fits

Typical backends

An encoder upstream produces a binary blob that is broadcast to subscribed WebSocket clients.

Per-tick blobs are gathered into a batch by collect, then fanned out element by element and POSTed to a downstream collector over HTTP.

Caveats

I/O contractThe WebSocket frame and HTTP body are the byte value exactly — no envelope, length prefix, or base64 — so consumers must know how to frame it. When the upstream sends a list, each element is delivered as its own message on every active channel in order, and an empty list delivers nothing.
Hard constraintEach entry in transports must be the websocket or http channel; any other value aborts startup, and including the http channel with an empty url silently skips the POSTs while the broadcast continues.
FallbackHTTP delivery is asynchronous with bounded exponential-backoff retries; when the queue is full the oldest pending request is dropped instead of blocking.
LimitationThe broadcast goes to every connected subscriber with no per-client filtering and no backfill for clients that connect late.
State lifetimeOnly url can be changed at runtime; the other keys are captured once at startup.

Versions

a80be355latestdefault
Serve the stream through the shared egress listener
7/30/2026