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
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
//! # Hello / Welcome / Ready Handshake -- Spec §5.2 – §5.5
//!
//! This module defines the data structures for the three-phase connection
//! handshake in the Rift/1 protocol:
//!
//! 1. **Hello** (§5.2) -- sent by the client to initiate the connection,
//! advertising its protocol version, supported codecs, authentication
//! modes, and optional resume information.
//! 2. **Welcome** (§5.3) -- sent by the server after successful
//! authentication, confirming the negotiated codec, session ID, and
//! resume window.
//! 3. **Ready** (§5.5) -- sent by the server after the session is fully
//! established, carrying runtime parameters such as heartbeat policy,
//! payload limits, and topic quotas.
//!
//! Between Welcome and Ready the server may optionally perform a
//! **Resume** exchange (§5.4), the result of which is reported as a
//! [`ResumeResult`].
//!
//! ## Connection Lifecycle
//!
//! ```text
//! Client Server
//! │ │
//! │──── Hello ──────────────────>│ (auth + capabilities)
//! │ │
//! │<─── Welcome ─────────────────│ (session + codec)
//! │ │
//! │ [optional Resume exchange] │
//! │ │
//! │<─── Ready ───────────────────│ (limits + heartbeat)
//! │ │
//! │ [data frames flow] │
//! ```
use BTreeMap;
use crateCodec;
/// Client Hello frame -- spec §5.2.
///
/// The `Hello` frame is the very first frame sent by the client after
/// opening the transport connection. It advertises the client's
/// capabilities so the server can choose appropriate negotiation
/// parameters.
///
/// ## Construction
///
/// Use [`Hello::new`] to create a Hello with the mandatory fields
/// populated (protocol name, encoded version, and codec list). All
/// other fields default to `None` or empty.
///
/// ## Fields
///
/// Most fields are optional. The server will use its own defaults when
/// a field is absent. See individual field documentation for details.
/// Authentication mode offered by the client or accepted by the server.
///
/// During the Hello exchange the client lists the authentication modes
/// it supports. The server picks one (or rejects the connection) and
/// may include the chosen mode in the Welcome response.
/// SDK identification metadata -- spec §5.2 (`sdk` field).
///
/// The client may include this information in its Hello frame so the
/// server can track SDK versions across its fleet, issue deprecation
/// warnings, and collect usage telemetry.
/// Server Welcome frame -- spec §5.3.
///
/// The `Welcome` frame is sent by the server immediately after
/// successful authentication. It confirms the negotiated parameters
/// and assigns the session.
///
/// ## Resume Window
///
/// The `resume_window_ms` field tells the client how long the server
/// will retain session state after disconnection, enabling the client
/// to reconnect and resume without losing messages.
/// Result of a session resume attempt -- spec §5.4.
///
/// When the client includes a `session_id` in its Hello, the server
/// attempts to restore the previous session. The outcome is reported
/// as one of these variants.
/// Server Ready frame -- spec §5.5.
///
/// The `Ready` frame is the final handshake frame. It is sent by the
/// server after the session is fully established (and any resume
/// exchange is complete). It carries the runtime parameters the client
/// needs to operate correctly on this connection.
///
/// After receiving Ready the client may begin publishing and
/// subscribing to topics.