Skip to content

ADR 0002: Browser-heavy DSP with a small appliance gateway

  • Status: accepted
  • Date: 2026-08-24

Decision

Use a browser-heavy architecture. A future small native rfsentry-api gateway will authenticate/control sessions, translate rtl_tcp control, frame IQ, expose receiver metadata, and enforce leases. Spectrum, waterfall, ordinary demodulation, detection, scan candidate ranking, and browser-capable decoders belong in Web Workers/WASM where practical.

The gateway must connect to the existing public demand endpoints on loopback:

browser -> TLS/WebSocket gateway -> 127.0.0.1:1234 or :1235
                                -> sdr-demandd -> serial-keyed rtl_tcp backend

It must not open RTL-SDR USB devices, start services, or use private backend ports 11234/11235. sdr-demandd retains wake-up, serial verification, active-client protection, clean close, and idle power-down authority.

Power and failure boundary

Phase 0 is replay-only and creates no daemon. Later, the gateway should be socket-activated or otherwise idle at zero recurring DSP load. A browser crash or WebSocket loss must close the upstream public-port connection so the normal idle timer can run. Each physical receiver continues to allow one data client.