Expand description
MACRO-2.B3 · the in-process transport.
A plexus_client::Transport that dispatches straight into an
Activation — no socket, no server process, no runtime setup. It is
the test double for a generated client, and the transport an activation
author reaches for first.
§Why it lives here and not in plexus-client
plexus-client must build for wasm32-unknown-unknown, so it cannot
depend on plexus-core. The dependency only runs one way — plexus-core → plexus-client — so the adapter that needs both lives on this side of
the seam. The other transports follow the same rule: each lives where its
dependencies do.
§The error layers, preserved
The three transports are meant to be interchangeable, which means they must agree on which layer a failure belongs to:
| Failure | Layer | Why |
|---|---|---|
Activation::call returns Err(PlexusError) | transport | the request never produced a stream — unknown method, dispatch refused, scope gate denied. Same class as “the connection failed”. |
the stream contains a PlexusStreamItem::Error | in-band | the activation answered, and the answer is an error. |
the MethodRef’s namespace is not this activation’s | transport | nothing was dispatched. |
Collapsing the first two would make this transport report a different error layer than the wire ones for the same failure.
§Not a way to skip the hub
DynamicHub applies the scope gate, provenance and credential-envelope
assembly. This transport applies none of them: it is Activation::call
and nothing else. Reaching for it outside a test is a smell.
Structs§
- InProcess
Transport - A
Transportbacked directly by oneActivation.