Skip to main content

Module types

Module types 

Source
Expand description

The words the rest of the crate keys on.

Five leaf types, each a plain Copy value with no behaviour: which side of the proxy a frame moves over, which of the two connections a call is about, which kind of data stream is being read, what a framed object is, and why the framer stopped framing one. Twenty-eight use edges from fourteen modules reach for them.

Nothing here imports anything from this crate, which is the property that keeps those edges pointing one way. A leaf type living wherever it was first needed reverses them instead: framer taking a field of its own output type from parser::data, event taking two fields of an event from framer and transport.

Every one of the five is also re-exported from the module that owns its subject, so event::ProxySide, transport::Leg, framer::ObjectMeta, framer::BypassReason and parser::data::DataStreamType all resolve. A downstream match on ProxySide with no wildcard arm keeps compiling, and nothing outside this crate has to move.

Structs§

ObjectMeta
A framed object’s identity and framing, without its payload.

Enums§

BypassReason
Why ObjectFramer stopped parsing a stream.
DataStreamType
The expected type of data stream.
Leg
Which of the proxy’s two connections a call is about.
ProxySide
Which side of the proxy a message originates from.