Expand description
Sync cycle orchestration.
Runs a single sync cycle (gate + push local changes, pull remote changes,
manage snapshots) and initializes sync infrastructure. All connection access
goes through the owned Database. Local changes are published from the
durable pending-changeset journal, which each host write appends to inside its
own journaled transaction — so a host write landing mid-cycle is captured for
the next outgoing changeset, while the pull’s apply is a plain connection write
that is never journaled and so never echoes applied rows.
Structs§
- Prepared
Sync Components - A sync session whose local and cloud representation has been validated before Store creation or opening can perform protocol work.
- Sync
Components - Components needed to run sync cycles.
- Sync
Cycle Failure - Sync
Cycle Result - Result of a single sync cycle.
Enums§
- Init
Sync Error - Store
Initialization - Establish the storage representation and signed owner anchor over an
already-built
CloudSyncConnection, returning the only runnable sync session.