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
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
//! Request metadata and streaming body types for handler consumption.
//!
//! These types allow handlers to consume request payloads incrementally
//! rather than waiting for full reassembly. See ADR 0002 for the design
//! rationale and composition with transport-level fragmentation.
//!
//! # Streaming request bodies
//!
//! Handlers can opt into streaming by accepting a [`RequestBodyStream`]
//! alongside [`RequestParts`]. The framework provides chunks via a bounded
//! channel, propagating back-pressure when the handler consumes slowly.
//!
//! ```
//! use bytes::Bytes;
//! use wireframe::request::{RequestBodyStream, RequestParts};
//!
//! async fn handle_upload(parts: RequestParts, body: RequestBodyStream) {
//! // Process metadata immediately
//! let id = parts.id();
//! // Consume body chunks incrementally via StreamExt or AsyncRead adapter
//! }
//! ```
use ;
use Bytes;
use Stream;
use ;
use StreamReader;
/// Streaming request body.
///
/// Handlers can consume this stream incrementally rather than waiting for
/// full body reassembly. Each item yields either a chunk of bytes or an
/// I/O error.
///
/// This type is symmetric with [`crate::response::FrameStream`] for streaming
/// responses.
/// See ADR 0002 for design rationale.
///
/// # Examples
///
/// ```
/// use bytes::Bytes;
/// use futures::StreamExt;
/// use wireframe::request::RequestBodyStream;
///
/// async fn consume_stream(mut body: RequestBodyStream) {
/// while let Some(result) = body.next().await {
/// match result {
/// Ok(chunk) => { /* process chunk */ }
/// Err(e) => { /* handle I/O error */ }
/// }
/// }
/// }
/// ```
pub type RequestBodyStream = ;
/// Default capacity for streaming request body channels.
///
/// This value balances memory usage against throughput; handlers consuming
/// slowly will cause back-pressure after this many chunks buffer.
///
/// # Rationale
///
/// The value 16 was chosen based on common workload characteristics:
///
/// - **Memory efficiency**: With typical chunk sizes of 4–16 KiB, 16 buffered chunks consume at
/// most ~256 KiB per connection, which is acceptable for most server deployments.
///
/// - **Throughput smoothing**: A small buffer absorbs transient processing delays in handlers,
/// preventing socket stalls on bursty workloads.
///
/// - **Back-pressure responsiveness**: The buffer is small enough that back-pressure engages
/// promptly when handlers fall behind, protecting the server from memory exhaustion.
///
/// - **Power-of-two alignment**: Matches common allocator bucket sizes, avoiding internal
/// fragmentation in the channel implementation.
///
/// Adjust via [`body_channel`] when your workload has different
/// characteristics (for example, very large chunks or strict memory limits).
pub const DEFAULT_BODY_CHANNEL_CAPACITY: usize = 16;
/// Create a bounded channel for streaming request bodies.
///
/// Returns a sender (for the connection to push chunks) and a
/// [`RequestBodyStream`] (for the handler to consume). Back-pressure
/// propagates when the channel fills: senders await capacity before
/// buffering additional chunks.
///
/// # Arguments
///
/// * `capacity` - Maximum number of chunks to buffer before applying back-pressure. Must be greater
/// than zero.
///
/// # Panics
///
/// Panics if `capacity` is zero, mirroring [`tokio::sync::mpsc::channel`].
///
/// # Examples
///
/// ```
/// use bytes::Bytes;
/// use wireframe::request::body_channel;
///
/// let (tx, rx) = body_channel(8);
/// // tx: send chunks from connection
/// // rx: consume in handler
/// ```
/// Adapter wrapping a [`RequestBodyStream`] as [`AsyncRead`].
///
/// Protocol crates can use this to feed streaming bytes into parsers
/// that operate on readers rather than streams. The adapter consumes
/// chunks from the underlying stream and presents them as a contiguous
/// byte sequence.
///
/// # Examples
///
/// ```
/// use bytes::Bytes;
/// use tokio::io::AsyncReadExt;
/// use wireframe::request::{RequestBodyReader, RequestBodyStream};
///
/// async fn read_all(body: RequestBodyStream) -> std::io::Result<Vec<u8>> {
/// let mut reader = RequestBodyReader::new(body);
/// let mut buf = Vec::new();
/// reader.read_to_end(&mut buf).await?;
/// Ok(buf)
/// }
/// ```
/// Request metadata extracted outwith the request body.
///
/// `RequestParts` separates routing and protocol metadata from the request
/// payload, enabling handlers to begin processing before the full body
/// arrives. This struct is the counterpart to streaming response types
/// ([`crate::response::Response::Stream`]) for the inbound direction.
///
/// # Differences from [`crate::app::PacketParts`]
///
/// - [`crate::app::PacketParts`] carries the raw `payload` for packet routing and envelope
/// reconstruction.
/// - `RequestParts` carries protocol-defined `metadata` bytes (for example headers) that handlers
/// need to interpret the body, but excludes the body itself.
///
/// # Examples
///
/// ```
/// use wireframe::request::RequestParts;
///
/// let parts = RequestParts::new(42, Some(123), vec![0x01, 0x02]);
/// assert_eq!(parts.id(), 42);
/// assert_eq!(parts.correlation_id(), Some(123));
/// assert_eq!(parts.metadata(), &[0x01, 0x02]);
/// ```
/// Result of correlation ID selection when inheriting from a source.