protocol-selection
Installation
SKILL.md
Protocol Selection
Overview
ovstream supports five transports in one library. You pick at runtime by passing the appropriate ServerType to Server() / ovstream_create_server(). You can run several simultaneously off the same CUDA buffer.
Decision matrix
| Need | Pick |
|---|---|
| Browser client, low setup friction | WebRTC |
| Industry-standard tools (VLC, ffplay), no input | RTSP |
| Lowest latency, native StreamSDK client | Native |
| Same-machine, zero-encode, host-resident pixels (CPU consumer) | SHM |
| Same-host, zero-encode, GPU-resident pixels (kernel/simulation consumer in another process or container) | CUDASHM |
If unsure, start with WebRTC — it has the broadest client compatibility (browsers, the bundled examples/webrtc_client/), supports input and message channels, and is what the examples default to.