Available on crate feature
reassembler only.Expand description
Sync TCP reassembly hooks.
Reassembler is the trait users implement to consume TCP byte
streams from one direction of one session. BufferedReassembler
is the simplest possible impl: in-order accumulation into a
Vec<u8>, with out-of-order segments dropped.
For tokio users with backpressure needs, see netring’s
AsyncReassembler and channel_factory.
Structs§
- Buffered
Reassembler - Built-in: drop OOO segments, accumulate in-order bytes into a
Vec<u8>per direction. Drain viatake. - Buffered
Reassembler Factory - Default factory that builds a fresh
BufferedReassemblerper (flow, side). Useful when you want byte buffers without implementing a custom factory. - Noop
Reassembler - Discards every segment without buffering. Used by the unified
crate::driver::Driveras the centralFlowDriver’s reassembler factory when the driver itself doesn’t need byte-stream reassembly — that work happens inside each registered slot’s ownFlowSessionDriver. Plan-116 support. - Noop
Reassembler Factory - Factory for
NoopReassembler. New in 0.10.0.
Traits§
- Reassembler
- Receives TCP segments for one direction of one session. Sync —
implementors don’t await; for blocking consumers (Vec buffer,
std::sync::mpsc, sync protocol parsers). - Reassembler
Factory - Build a
Reassemblerfor a brand-new session, given its key and side. Modeled after gopacket’sStreamFactory.