Struct InboxDoc 

pub struct InboxDoc {
    pub entries: Vec<InboxEntry>,
    pub window: Option<Window>,
    pub boundary_request: Option<VerbRequest>,
    pub sync_request: Option<VerbRequest>,
}

Fields

entries: Vec<InboxEntry>

window: Option<Window>

boundary_request: Option<VerbRequest>

“Please publish” from outside the pod (§2.5). Deliberately a FIELD and not a fake no-object InboxEntry: consume_inbox HEADs file_key(path) for every entry, so an entry naming no object lands in the NotFound arm as a spurious consume-object-missing conflict — and special-casing the single most safety-critical function in the crate to avoid that is worse than either.

sync_request: Option<VerbRequest>

“Please pull” from outside the pod — CARRIED, never performed (D14). A boundary publishes what is already on disk and touches no local file; sync re-derives the tree against the current remote manifest and DELETES local files for remotely-deleted paths. Performing that on a remote’s say-so would upgrade what a leaked gateway bearer can do from “publish, plus hand over these N named objects” to “rewrite and delete across a running agent’s tree, at my timing, under a scope I choose”.

Trait Implementations

impl Clone for InboxDoc

fn clone(&self) -> InboxDoc

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for InboxDoc

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

Formats the value using the given formatter.

impl Default for InboxDoc

fn default() -> InboxDoc

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for InboxDoc

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for InboxDoc

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.