pub trait ComponentRunnerClientSender {
type Transport: Transport;
// Required method
fn start<___R>(
&self,
request: &mut ___R,
) -> Result<SendFuture<'_, Self::Transport>, EncodeError>
where ___R: Encode<<Self::Transport as Transport>::SendBuffer, Encoded = WireComponentRunnerStartRequest>;
}
Expand description
A helper trait for the ComponentRunner
client sender.
Required Associated Types§
Required Methods§
Sourcefn start<___R>(
&self,
request: &mut ___R,
) -> Result<SendFuture<'_, Self::Transport>, EncodeError>where
___R: Encode<<Self::Transport as Transport>::SendBuffer, Encoded = WireComponentRunnerStartRequest>,
fn start<___R>(
&self,
request: &mut ___R,
) -> Result<SendFuture<'_, Self::Transport>, EncodeError>where
___R: Encode<<Self::Transport as Transport>::SendBuffer, Encoded = WireComponentRunnerStartRequest>,
Start running a component instance described by start_info
.
Component manager binds and uses controller
to control the
lifetime of the newly started component instance.
Errors are delivered as epitaphs over the ComponentController
protocol. In the event of an error, the runner must ensure that
resources are cleaned up.
Dyn Compatibility§
This trait is not dyn compatible.
In older versions of Rust, dyn compatibility was called "object safety", so this trait is not object safe.
Implementations on Foreign Types§
Source§impl<___T> ComponentRunnerClientSender for ClientSender<___T, ComponentRunner>where
___T: Transport,
impl<___T> ComponentRunnerClientSender for ClientSender<___T, ComponentRunner>where
___T: Transport,
Source§fn start<___R>(
&self,
request: &mut ___R,
) -> Result<SendFuture<'_, Self::Transport>, EncodeError>where
___R: Encode<<Self::Transport as Transport>::SendBuffer, Encoded = WireComponentRunnerStartRequest>,
fn start<___R>(
&self,
request: &mut ___R,
) -> Result<SendFuture<'_, Self::Transport>, EncodeError>where
___R: Encode<<Self::Transport as Transport>::SendBuffer, Encoded = WireComponentRunnerStartRequest>,
Start running a component instance described by start_info
.
Component manager binds and uses controller
to control the
lifetime of the newly started component instance.
Errors are delivered as epitaphs over the ComponentController
protocol. In the event of an error, the runner must ensure that
resources are cleaned up.