syncular-client 0.31.0

Syncular v2 Rust client core on rusqlite, implemented from SPEC.md alone (language-neutrality POC, stage 2)
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
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78

//! # syncular-client — Syncular v2 Rust client core (POC stage 2)
//!
//! A clean-room client implementation of the SPEC.md client-behavior
//! contract on rusqlite local storage, consuming the committed `ssp2`
//! codec as its wire layer. Built without reading the v1 Rust tree or the
//! v2 TypeScript client — the conformance catalog (packages/conformance)
//! is the proof that both cores implement one written protocol.
//!
//! Blocking hosts drive `sync()` / `sync_until_idle()`. Mailbox hosts prepare
//! a round on the owner, run `PreparedSyncRound::exchange` on an I/O executor,
//! and apply the result on the owner. An upload continuation repeats that
//! exchange/apply cycle before the captured metadata request. The owner can
//! serve local commands throughout; it queues inbound realtime traffic until
//! the round completes. Scheduling is host policy (§8.4).

pub mod api;
#[cfg(feature = "bench-internals")]
mod bench;
pub mod client;
/// §5.10.5 native CRDT helpers (the `crdt-yjs` feature) — the Rust face of the
/// Yjs binding, mirroring `@syncular/crdt-yjs`. Off by default (dependency-lean).
#[cfg(feature = "crdt-yjs")]
pub mod crdt;
/// Shared blocking HTTP/WebSocket host transport for Rust-backed bindings.
/// The network stack is feature-gated; its no-network shape remains available
/// in dependency-lean builds so host code needs only one transport type.
pub mod native_transport;
mod progress;
mod round;
pub use progress::{
    ProgressObserver, ProgressPhase, ProgressState, ProgressSubscription, SyncProgress,
    SyncProgressListener,
};
pub use round::{AppliedSyncRound, CompletedSyncRound, PreparedSyncRound};
/// RFC 0005 previous-version context: the persisted schema descriptor, the
/// bounded capture, and the sibling container FILE beside the replica.
pub mod previous_version;
pub mod query_guard;
pub mod realtime_round;
pub mod remote;
pub mod schema;
pub mod transport;
pub mod values;

pub use api::{
    creation_time_bucket, last, AuthorityReadDeclaration, ClientChangeBatch, ClientDiagnosticsHost,
    ClientDiagnosticsLease, ClientDiagnosticsReplica, ClientDiagnosticsRequest,
    ClientDiagnosticsSchema, ClientDiagnosticsSnapshot, ClientDiagnosticsStorage, ClientError,
    ClientLimits, CommandEffects, CommitDelivery, CommitOperation, CommitOperationOutcome,
    CommitOutcome, CommitOutcomeQuery, CommitOutcomeResolution, CommitOutcomeStatus,
    ConflictRecord, CoverageSnapshot, DiagnosticLastChange, DiagnosticLastRound,
    DiagnosticQueryFailure, DiagnosticRoundCounters, DiagnosticSubscription,
    ExpectedDiagnosticSubscription, FetchedBlob, LocalDataPurgeInput, LocalDataPurgeResult,
    LocalDataPurgeTarget, LocalDataRebootstrapInput, LocalDataRebootstrapResult, Mutation,
    PresencePeer, QueryOwner, QueryReadFailure, QueryRow, QuerySnapshot, QueryValue,
    RealtimePolicy, RealtimeState, RejectionRecord, ResolveCommitOutcomeInput, RetainedCommitRow,
    RetainedUniqueConflict, RowState, SchemaFloor, SnapshotRead, SubscriptionCatchup,
    SubscriptionStateView, SyncIntent, SyncOutcome, SyncReport, SyncStatusSnapshot, TableChange,
    TimeBucketUnit, WindowBase, WindowChange, WindowCoverage, WindowState, WindowUnitRef,
    CLIENT_DIAGNOSTICS_VERSION, MAX_DIAGNOSTIC_EXPECTED_SUBSCRIPTIONS,
    MAX_DIAGNOSTIC_QUERY_FAILURES, REALTIME_LOST_CODE, REALTIME_UNAVAILABLE_CODE,
};
pub use client::{
    FileQuerySnapshotReader, SnapshotReadRequest, SnapshotStatement, SyncClient,
    SECURITY_PREFLIGHT_REQUIRED_CODE,
};
pub use schema::{compile_schema, parse_schema_json, ClientSchema};
pub use transport::{BlobDownload, BlobUploadGrant, SegmentRequest, Transport, TransportError};

// Re-export the SSP2 stream scanner (§8.7 round-response reassembly) so the
// native transports (FFI + Tauri plugin) reach it through their existing
// `syncular-client` dependency, without each adding a direct `ssp2` path dep.
pub use realtime_round::{RealtimeRound, RoundInbound, REALTIME_TAG_DELTA, REALTIME_TAG_ROUND};
pub use remote::{
    PreparedRemoteCommit, RemoteBytes, RemoteClientError, RemoteCommandResult, RemoteCommitInput,
    RemoteCommitResult, RemoteQueryResult, SyncRemoteClient,
};
pub use ssp2::{MessageStreamScanner, ScannedMessage};