Struct quic_rpc::server::RpcChannel

pub struct RpcChannel<S: Service, C: ServiceEndpoint<S>, SInner: Service = S> {
    pub send: C::SendSink,
    pub recv: C::RecvStream,
    pub map: Arc<dyn MapService<S, SInner>>,
}

A channel for requests and responses for a specific service.

This just groups the sink and stream into a single type, and attaches the information about the service type.

Sink and stream are independent, so you can take the channel apart and use them independently.

Fields

send: C::SendSink

Sink to send responses to the client.

recv: C::RecvStream

Stream to receive requests from the client.

map: Arc<dyn MapService<S, SInner>>

Mapper to map between S and S2

Implementations

impl<S, C> RpcChannel<S, C, S>

where S: Service, C: ServiceEndpoint<S>,

pub fn new(send: C::SendSink, recv: C::RecvStream) -> Self

Create a new RPC channel.

impl<S, C, SInner> RpcChannel<S, C, SInner>

where S: Service, C: ServiceEndpoint<S>, SInner: Service,

pub fn map<SNext>(self) -> RpcChannel<S, C, SNext>

where SNext: Service, SNext::Req: Into<SInner::Req> + TryFrom<SInner::Req>, SNext::Res: Into<SInner::Res> + TryFrom<SInner::Res>,

Map this channel’s service into an inner service.

This method is available if the required bounds are upheld: SNext::Req: IntoSInner::Req + TryFromSInner::Req, SNext::Res: IntoSInner::Res + TryFromSInner::Res,

Where SNext is the new service to map to and SInner is the current inner service.

This method can be chained infintely.

impl<S, C, SInner> RpcChannel<S, C, SInner>

where S: Service, C: ServiceEndpoint<S>, SInner: Service,

pub async fn bidi_streaming<M, F, Str, T>( self, req: M, target: T, f: F ) -> Result<(), RpcServerError<C>>

where M: BidiStreamingMsg<SInner>, F: FnOnce(T, M, UpdateStream<S, C, M::Update, SInner>) -> Str + Send + 'static, Str: Stream<Item = M::Response> + Send + 'static, T: Send + 'static,

handle the message M using the given function on the target object

If you want to support concurrent requests, you need to spawn this on a tokio task yourself.

impl<S, C, SInner> RpcChannel<S, C, SInner>

where S: Service, C: ServiceEndpoint<S>, SInner: Service,

pub async fn client_streaming<M, F, Fut, T>( self, req: M, target: T, f: F ) -> Result<(), RpcServerError<C>>

where M: ClientStreamingMsg<SInner>, F: FnOnce(T, M, UpdateStream<S, C, M::Update, SInner>) -> Fut + Send + 'static, Fut: Future<Output = M::Response> + Send + 'static, T: Send + 'static,

handle the message M using the given function on the target object

If you want to support concurrent requests, you need to spawn this on a tokio task yourself.

impl<S, C, SInner> RpcChannel<S, C, SInner>

where S: Service, C: ServiceEndpoint<S>, SInner: Service,

pub async fn rpc<M, F, Fut, T>( self, req: M, target: T, f: F ) -> Result<(), RpcServerError<C>>

where M: RpcMsg<SInner>, F: FnOnce(T, M) -> Fut, Fut: Future<Output = M::Response>, T: Send + 'static,

handle the message of type M using the given function on the target object

If you want to support concurrent requests, you need to spawn this on a tokio task yourself.

pub async fn rpc_map_err<M, F, Fut, T, R, E1, E2>( self, req: M, target: T, f: F ) -> Result<(), RpcServerError<C>>

where M: RpcMsg<SInner, Response = Result<R, E2>>, F: FnOnce(T, M) -> Fut, Fut: Future<Output = Result<R, E1>>, E2: From<E1>, T: Send + 'static,

A rpc call that also maps the error from the user type to the wire type

This is useful if you want to write your function with a convenient error type like anyhow::Error, yet still use a serializable error type on the wire.

impl<S, C, SInner> RpcChannel<S, C, SInner>

where S: Service, C: ServiceEndpoint<S>, SInner: Service,

pub async fn server_streaming<M, F, Str, T>( self, req: M, target: T, f: F ) -> Result<(), RpcServerError<C>>

where M: ServerStreamingMsg<SInner>, F: FnOnce(T, M) -> Str + Send + 'static, Str: Stream<Item = M::Response> + Send + 'static, T: Send + 'static,

handle the message M using the given function on the target object

If you want to support concurrent requests, you need to spawn this on a tokio task yourself.

impl<S, C, SInner> RpcChannel<S, C, SInner>

where S: Service, C: ServiceEndpoint<S>, SInner: Service,

pub async fn try_server_streaming<M, F, Fut, Str, T>( self, req: M, target: T, f: F ) -> Result<(), RpcServerError<C>>

where M: TryServerStreamingMsg<SInner>, Result<M::Item, M::ItemError>: Into<SInner::Res> + TryFrom<SInner::Res>, Result<StreamCreated, M::CreateError>: Into<SInner::Res> + TryFrom<SInner::Res>, F: FnOnce(T, M) -> Fut + Send + 'static, Fut: Future<Output = Result<Str, M::CreateError>> + Send + 'static, Str: Stream<Item = Result<M::Item, M::ItemError>> + Send + 'static, T: Send + 'static,

handle the message M using the given function on the target object

If you want to support concurrent requests, you need to spawn this on a tokio task yourself.

Compared to RpcChannel::server_streaming, with this method the stream creation is via a function that returns a future that resolves to a stream.

Trait Implementations

impl<S: Debug + Service, C: Debug + ServiceEndpoint<S>, SInner: Debug + Service> Debug for RpcChannel<S, C, SInner>

where C::SendSink: Debug, C::RecvStream: Debug,

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.