Struct sync15::bso::IncomingContent

pub struct IncomingContent<T> {
    pub envelope: IncomingEnvelope,
    pub kind: IncomingKind<T>,
}

We also have the concept of “content”, which helps work with a T which is represented inside the payload. Real-world examples of a T include Bookmarks or Tabs. See the content module for the implementations.

So this all flows together in the following way:

• Incoming encrypted data: EncryptedIncomingBso -> IncomingBso -> [specific engine] -> IncomingContent
• Incoming cleartext data: IncomingBso -> IncomingContent (Note that incoming cleartext only happens for a few collections managed by the sync client and never by specific engines - engine BSOs are always encryted)
• Outgoing encrypted data: OutgoingBso (created in the engine) -> [this crate] -> EncryptedOutgoingBso
• Outgoing cleartext data: just an OutgoingBso with no conversions needed. IncomingContent is the result of converting an IncomingBso into some - it consumes the Bso, so you get the envelope, and the IncomingKind which reflects the state of parsing the json.

Fields

envelope: IncomingEnvelope

kind: IncomingKind<T>

Implementations

impl<T> IncomingContent<T>

pub fn content(self) -> Option<T>

Returns Some(content) if [self.kind] is IncomingKind::Content, None otherwise.

Trait Implementations

impl<T: Debug> Debug for IncomingContent<T>

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

Formats the value using the given formatter.