Struct kernel::registry::Envelope

#[non_exhaustive]
pub struct Envelope<P> {
    pub body: P,
    service_id: ServiceId,
    client_id: ClientId,
    request_id: RequestResponseId,
}

A wrapper for a message TO and FROM a driver service. Used to be able to add additional message metadata without changing the fundamental message type.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

body: P

service_id: ServiceId

client_id: ClientId

request_id: RequestResponseId

Implementations

impl<P> Envelope<P>

fn split_reply<R>(self) -> (P, OpenEnvelope<R>)

pub fn reply_with<U>(&self, body: U) -> Envelope<U>

Create a response Envelope from a given request Envelope.

Maintains the same Service ID and Client ID, and increments the request ID by one.

pub fn reply_with_body<F, U>(self, f: F) -> Envelope<U>

where F: FnOnce(P) -> U,

Create a response Envelope from a given request Envelope.

Maintains the same Service ID and Client ID, and increments the request ID by one.

This variant also gives you the request body in case you need it for the response.