Enum RecoveryOutcome 

#[non_exhaustive]
pub enum RecoveryOutcome {
    Exact,
    Duplicated {
        suppressed: u64,
    },
    Gap {
        missing: u64,
    },
}

The three ways a recovery can turn out.

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.

Exact

The server resumed exactly where the client asked. Nothing was lost and nothing was duplicated: continuity is intact.

Duplicated

The server resumed earlier than asked, which it is allowed to do, and re-sent notifications the client already had. This client discarded them before you saw them, so continuity is still intact [docs/spec/02-session-lifecycle.md §5.2].

Fields

suppressed: u64

How many re-delivered notifications were suppressed.

Gap

The server resumed later than asked: the notifications in between are gone and will not arrive.

State derived from the affected subscriptions may be stale. The protocol does not say this can happen and does not say what a client should do about it, so this crate reports it rather than deciding for you [docs/spec/02-session-lifecycle.md §5.4].

Fields

missing: u64

How many notifications were skipped.

Trait Implementations

impl Clone for RecoveryOutcome

fn clone(&self) -> RecoveryOutcome

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Copy for RecoveryOutcome

impl Debug for RecoveryOutcome

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

Formats the value using the given formatter.

impl Eq for RecoveryOutcome

impl PartialEq for RecoveryOutcome

fn eq(&self, other: &RecoveryOutcome) -> bool

Equality operator ==.

fn ne(&self, other: &Rhs) -> bool

Inequality operator !=.

impl StructuralPartialEq for RecoveryOutcome