ubiquisync-core 0.0.3

Core protocol types and sync engine for Ubiquisync — conflict-free sync of structured data over commodity cloud storage or a dedicated server.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34

//! Wire-level log entry: a single op with timestamp and optional
//! server-attested user attribution. This is the unit of encoding/decoding in a
//! segment file.

use crate::hlc::Timestamp;
use crate::uuid::Uuid;

/// A single log entry: one operation plus metadata. This is the unit
/// written to and read from segment files — each entry has its own
/// blake3 hash and can be independently expunged.
///
/// The entry is generic over its op vocabulary `E`: each data domain defines
/// its own op type and carries it in this envelope — for example the table
/// op vocabulary in `ubiquisync-tables`. Any domains in use share one HLC
/// clock domain, so timestamps are causally comparable across them.
#[derive(Debug, Clone, PartialEq, Eq)]
pub struct LogEntry<E> {
    /// The **server-attested** user id for this entry. Every entry originates
    /// from *some* user, but this field specifically carries the identity a
    /// server vouched for — it is populated only in server-mode segments, where
    /// the server asserts attribution. `None` in device mode, where attribution
    /// is implicit from the peer directory and no server assertion exists.
    ///
    /// Do not read this as "the author"; read it as "who the server said this
    /// was." It is distinct from a stream's `peer_id` (which stream the entry
    /// came from).
    pub server_user_id: Option<Uuid>,
    /// HLC timestamp — monotonically non-decreasing within a peer's stream.
    /// Entries written in one atomic transaction share a tick, so they are
    /// treated as one logical write by LWW comparisons.
    pub timestamp: Timestamp,
    /// The state mutation.
    pub op: E,
}