agent-mesh-bus 0.8.0

High-level pub/sub + request-reply API for agent-mesh
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

//! High-level pub/sub + request-reply over the agent-mesh transport.
//!
//! This commit lands the application-level message dispatch surface
//! ([`Inbox`], [`BusMessage`]). The high-level [`Bus`] type that
//! drives it lands in the next commit.
//!
//! What's already in place from prior commits:
//!
//! 1. **Topic namespacing** ([`Topic`]) — every pub/sub name is
//!    scoped to the issuing user's fingerprint, so two unrelated
//!    users on the same LAN can never collide.
//! 2. **Replay defense** ([`replay::NonceCache`] +
//!    [`replay::SequenceTracker`]) — duplicate nonces and
//!    out-of-order sequence numbers from a known peer are rejected.

#![doc(html_root_url = "https://docs.rs/agent-mesh-bus")]

pub mod bus;
pub mod error;
pub mod inbox;
pub mod replay;
pub mod reply;
pub mod sequence;
pub mod session;
pub mod topic;
pub mod transport;

#[cfg(feature = "pyo3")]
pub mod pyo3_module;

pub use bus::{Bus, BusOptions, IrohTransport, PeerEndpoint};
pub use error::{BusError, Result};
pub use inbox::{BusMessage, Inbox, OutgoingReply, RequestContext};
pub use reply::CorrelationId;
pub use sequence::{FileSequenceReservations, SequenceReservations};
pub use session::{IncomingSession, Session, SessionPeer, SessionReceiver, SessionSender};
pub use topic::Topic;
pub use transport::{
    AuthenticatedPeer, DeliveryProvenance, InMemoryTransport, Inbound, MeshNet, ReplyRoute,
    SessionStream, Transport,
};