docs: describe the TCP transport, multiplexing and TCPStreamJoin in README, architecture and StreamHub docs
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
1 parent
05b9490b06
commit
81879b8b7a
5 files changed
+66
-3
No files matched your search
@@ -63,6 +63,11 @@ Full streaming pipeline: MARTe2 (FileReader -> IOGAM -> UDPStreamer) -> StreamHu
|
||||
(live, zoom, window, trigger). The validator compares the recording against the analytic
|
||||
ground truth (fidelity, sine shape fit, continuity) and optionally a fed-reference tap.
|
||||
|
||||
Chain scenarios `s60`-`s73` use TCP transports (`network = "tcp"` or `"tcp_service"`). The
|
||||
optional `hub` field adds `{"mode": "mux"}` (the hub takes all sources over one multiplexed
|
||||
connection, `s72`) or `{"mode": "join"}` (a `TCPStreamJoin` merges the sources and the hub
|
||||
subscribes to the merge, `s73`).
|
||||
|
||||
### direct
|
||||
|
||||
MARTe2 FileReader -> UDPStreamer -> UDPStreamerClient -> FileWriter round-trip. Validates that
|
||||
|
||||
Reference in new issue
Block a user