Enum WatcherV4Request

pub enum WatcherV4Request {
    Watch {
        responder: WatcherV4WatchResponder,
    },
}

An observer protocol for changes in system’s IPv4 routing state.

Variants

Watch

Hanging-Get style API for observing routing changes.

Clients must only have one pending Watch call at a time. Calling Watch while a request is already pending will cause the protocol to close.

The first N events will always be existing where N is the number of IPv4 routes that already existed when the server-end of the protocol was initialized. The following event will be idle signaling the end of the existing events. At this point the client has watched all existing state and will never again observe an existing event.

Events are returned in batches of up to MAX_EVENTS events. There is no correlation between the batch size/boundary and it’s contents: it is perfectly valid for the server to split the block of existing events, across several batches. Clients should view this API as providing a stream of events, where batches are used to reduce IPC load on the system.

• response events A vector of at most MAX_EVENTS events.

Fields

responder: WatcherV4WatchResponder

Implementations

impl WatcherV4Request

pub fn into_watch(self) -> Option<WatcherV4WatchResponder>

pub fn method_name(&self) -> &'static str

Name of the method defined in FIDL

Trait Implementations

impl Debug for WatcherV4Request

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

Formats the value using the given formatter.