Enum Bridge 

#[non_exhaustive]
pub enum Bridge {
    Passthrough,
    Upgrade,
    Downgrade,
    Unsupported,
}

Available on crate feature hub only.

What a hub must do to a message crossing between two OCPI versions.

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.

Passthrough

Both sides speak the same version; forward the bytes unchanged.

This is the fast path, and the one that cannot lose anything.

Upgrade

The receiver speaks a newer version; upgrade.

Downgrade

The receiver speaks an older version; downgrade, and report what did not fit.

Unsupported

This build has no conversions between the two versions, so nothing can be translated.

Today that is any crossing involving OCPI 2.1.1 — which has no owner fields, no routing and no Price, so carrying an object across it is a decision about the deployment rather than a translation — or a version this crate does not model at all.

Relaying the bytes unchanged is still an option, and for two parties that understand each other by some arrangement outside this crate it is the right one; the decision belongs to the operator, so Forwarder takes it as Unbridgeable rather than assuming.

Trait Implementations

impl Clone for Bridge

fn clone(&self) -> Bridge

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Copy for Bridge

impl Debug for Bridge

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

Formats the value using the given formatter.

impl Eq for Bridge

impl PartialEq for Bridge

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

Equality operator ==.

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

Inequality operator !=.

impl StructuralPartialEq for Bridge