Module pipeline 

Re-exports

pub use network::egress::addressed_router::AddressedPushRouter;

pub use network::egress::addressed_router::AddressedRequest;

pub use network::egress::push_router::PushRouter;

pub use network::egress::push_router::RouterMode;

pub use crate::engine;

pub use crate::engine::AsyncEngine;

pub use crate::engine::AsyncEngineContext;

pub use crate::engine::AsyncEngineContextProvider;

pub use crate::engine::Data;

pub use crate::engine::DataStream;

pub use crate::engine::Engine;

pub use crate::engine::EngineStream;

pub use crate::engine::EngineUnary;

pub use crate::engine::ResponseStream;

pub use context::Context;

pub use error::PipelineError;

pub use error::PipelineErrorExt;

pub use error::TwoPartCodecError;

Modules

context

Context Module

error

Pipeline Error

network

TODO - we need to reconcile what is in this crate with distributed::transports

registry

Structs

Error

The Error type, a wrapper around a dynamic error type.

Event

PipelineNode

PipelineOperator

A PipelineOperator is a node that can transform both the forward and backward paths using the logic defined by the implementation of an Operator trait.

SegmentSink

SegmentSource

ServiceBackend

ServiceFrontend

A ServiceFrontend is the interface for an AsyncEngine<SingleIn<Context<In>>, ManyOut<Annotated<Out>>, Error>

Traits

AsyncTransportEngine

Operator

An Operator is a trait that defines the behavior of how two AsyncEngine can be chained together. An Operator is not quite an AsyncEngine because its generate method requires both the upstream request, but also the downstream AsyncEngine to which it will pass the transformed request. The Operator logic must transform the upstream request UpIn to the downstream request DownIn, then transform the downstream response DownOut to the upstream response UpOut.

PipelineIO

Sink

A Sink trait defines how data is received from a source and processed.

Source

A Source trait defines how data is emitted from a source to a downstream sink.

Type Aliases

BidirectionalStreamingEngine

BidirectionalStreaming takes multiple inputs and returns multiple outputs. Input and output values are considered independent of each other; however, they could be constrained to be related.

ClientStreamingEngine

ClientStreaming Engine is a pipeline that takes multiple inputs and returns a single output Typically the engine will consume the entire input stream; however, it can also decided to exit early and emit a response without consuming the entire input stream.

ManyIn

Pipeline inputs carry a Context which can be used to carry metadata or additional information about the request. This information propagates through the stages, both local and distributed.

ManyOut

Type alias for the output of pipeline that returns multiple values

ServerStreamingEngine

ServerStreaming takes a single input and returns multiple outputs.

Service

ServiceEngine

SingleIn

Pipeline inputs carry a Context which can be used to carry metadata or additional information about the request. This information propagates through the stages, both local and distributed.

SingleOut

Type alias for the output of pipeline that returns a single value

UnaryEngine

Unary Engine is a pipeline that takes a single input and returns a single output

Attribute Macros

async_trait