crafty-client 0.2.1

In-process and remote (HTTP/3) client API for crafty.
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

//! `crafty-client` — client handles for talking to a crafty cluster (client-api).
//!
//! Two layers over a shared [`crafty_proto`] wire contract (client-api):
//!
//! * **In-process (L1):** embed a node and use its `crafty_actor::NodeHandle`
//!   directly (`propose`/`query`) — no serialization, no network.
//! * **Remote (L2):** [`RemoteClient`] speaks `postcard` over any
//!   [`crafty_net`] transport (live QUIC/HTTP/3 with client mTLS, or the
//!   in-memory `LocalNetwork` in tests). A follower transparently forwards to
//!   the leader server-side (client-routing), so a client can connect to any node; the
//!   built-in [`RetryPolicy`] adds failover + leader-follow for elections and
//!   downed nodes.
//!
//! [`TypedClient`] wraps either layer with a
//! [`StateMachine`](crafty_core::StateMachine)'s command/query/response types.

pub use {crafty_core, crafty_net, crafty_proto};

mod batch;
mod error;
mod remote;
mod saga;
mod two_phase;
mod typed;

pub use batch::{BatchError, KeyedBatchStep, propose_keyed_batch};
pub use error::ClientError;
pub use remote::{Client, KeyedClient, RemoteClient, RetryPolicy};
pub use saga::{
    InMemorySagaJournal, ResumeSagaOpts, RunSagaOpts, SagaError, SagaEvent, SagaJournal,
    SagaJournalError, SagaJournalPhase, SagaJournalRecord, SagaOutcome, SagaPlan, SagaStep,
    decode_journal_record, encode_journal_record, resume_saga, run_saga,
};
pub use two_phase::{
    InMemoryTwoPhaseJournal, ResumeTwoPhaseOpts, RunTwoPhaseOpts, TwoPhaseClient, TwoPhaseError,
    TwoPhaseEvent, TwoPhaseJournal, TwoPhaseJournalError, TwoPhaseJournalRecord,
    decode_two_phase_journal_record, encode_two_phase_journal_record, propose_cross_shard_2pc,
    propose_cross_shard_2pc_with_opts, resume_cross_shard_2pc,
};
pub use typed::TypedClient;