1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
// SPDX-FileCopyrightText: Copyright (c) 2025-2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
// SPDX-License-Identifier: Apache-2.0
//! Frame-level transport abstraction for ordered delivery streaming.
//!
//! This module defines the [`FrameTransport`] trait boundary consumed by the
//! Velo streaming runtime and implemented by the in-tree
//! `TcpFrameTransport`, `GrpcFrameTransport`, and (deprecated) `VeloFrameTransport`.
//! Out-of-tree implementors (custom RDMA, hardware transports, alternative
//! streaming substrates) should `impl FrameTransport for MyTransport` against
//! this contract.
//!
//! # Endpoint resolution
//!
//! Streaming transports advertise their listener endpoint(s) into the local
//! [`WorkerAddress`] via [`FrameTransport::address`], keyed by the same
//! [`TransportKey`] returned by [`FrameTransport::key`]. The Velo builder
//! merges streaming entries into the local PeerInfo's WorkerAddress alongside
//! messenger transport entries.
//!
//! When a peer is registered (via `Velo::register_peer` or discovery), the
//! runtime calls [`FrameTransport::register`] on every installed streaming
//! transport. The transport extracts its own entry from the peer's
//! WorkerAddress, decodes the endpoint(s), and caches the resolved socket
//! address keyed by the peer's [`WorkerId`].
//!
//! [`FrameTransport::connect`] then looks up the cached address by
//! [`WorkerId`] — no endpoint string is exchanged on the streaming attach
//! handshake.
use Result;
use BoxFuture;
use crate;
/// Transport abstraction for frame-level ordered delivery.
///
/// # Ordered-Delivery Contract
///
/// All frames -- including data frames (`Item`, `Heartbeat`) **and** sentinel
/// frames (`Dropped`, `Detached`, `Finalized`, `TransportError`) -- MUST travel
/// the **same physical channel** established by [`FrameTransport::bind`] /
/// [`FrameTransport::connect`]. Sentinels MUST NOT be injected via a side
/// channel; the FIFO ordering guarantee of the underlying channel is
/// load-bearing for the correctness of the streaming protocol.
///
/// Implementations MUST preserve send order: a frame sent before another MUST
/// be received before that other frame on the corresponding
/// [`flume::Receiver`].
///
/// # Usage
///
/// The transport operates at the raw byte level. Callers are responsible for
/// serializing frame values to `Vec<u8>` before sending via
/// [`flume::Sender::send_async`], and for deserializing bytes received from
/// [`flume::Receiver::recv_async`].
///
/// # Async Design
///
/// Both `bind` and `connect` return [`BoxFuture`] to support async
/// implementations (e.g., network setup). The heap allocation is acceptable
/// because these are setup-path calls, not per-frame hot-path operations.