Enum ServiceEvent

#[non_exhaustive]
pub enum ServiceEvent<T: ServerTypes> {
    Read {
        peer_id: PeerId,
        handle: Handle,
        offset: u32,
        responder: T::ReadResponder,
    },
    Write {
        peer_id: PeerId,
        handle: Handle,
        offset: u32,
        value: T::ServiceWriteType,
        responder: T::WriteResponder,
    },
    ClientConfiguration {
        peer_id: PeerId,
        handle: Handle,
        notification_type: NotificationType,
    },
    #[non_exhaustive]
    PeerInfo {
        peer_id: PeerId,
        mtu: Option<u16>,
        connected: Option<bool>,
    },
}

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

Read

Peer requests to read from a handle (characteritic or descriptor) at the given offset.

Fields

peer_id: PeerId

handle: Handle

offset: u32

responder: T::ReadResponder

Write

Peer has written a value to a handle (characteristic or descriptor) at the given offset.

Fields

peer_id: PeerId

handle: Handle

offset: u32

value: T::ServiceWriteType

responder: T::WriteResponder

ClientConfiguration

Notification that a peer has configured a characteristic for indication or notification.

Fields

peer_id: PeerId

handle: Handle

notification_type: NotificationType

PeerInfo

Extra information about a peer is provided. This event may not be sent by all implementations.

Fields

Non-exhaustive enum variants could have additional fields added in future. Therefore, non-exhaustive enum variants cannot be constructed in external crates and cannot be matched against.

peer_id: PeerId

mtu: Option<u16>

connected: Option<bool>

Implementations

impl<T: ServerTypes> ServiceEvent<T>

pub fn peer_id(&self) -> PeerId

pub fn peer_info( peer_id: PeerId, mtu: Option<u16>, connected: Option<bool>, ) -> Self