Re-exports§
pub use crate::backend_v1::GetConfigurationRequest;pub use crate::backend_v1::GetConfigurationResponse;pub use crate::backend_v1::GetInboxIdsRequest;pub use crate::backend_v1::GetInboxIdsResponse;pub use crate::backend_v1::PublishRequest;pub use crate::backend_v1::PublishResponse;pub use crate::backend_v1::QueryNewestRequest;pub use crate::backend_v1::QueryNewestResponse;pub use crate::backend_v1::QueryRequest;pub use crate::backend_v1::QueryResponse;pub use crate::backend_v1::RecipientState;pub use crate::backend_v1::RegisterRequest;pub use crate::backend_v1::ServerEnvelope;pub use crate::backend_v1::UnregisterRequest;pub use crate::backend_v1::UnregisterResponse;pub use crate::backend_v1::UpdateSubscriptionsRequest;pub use crate::backend_v1::VerifySmartContractWalletSignaturesRequest;pub use crate::backend_v1::VerifySmartContractWalletSignaturesResponse;
Structs§
Traits§
- ApiBuilder
- Build an API from its parts for the XMTP Backend
- Boxable
Xmtp Api - NetConnect
Config - describe how to create a single network connection. Implement this trait if your type connects to a single network channel/connection (like gRPc or HTTP)
- XmtpApi
- Xmtp
Backend Client - The backend unary RPCs. Callers own retries and chunking.
- Xmtp
MlsBidi Streams - The XIP-83 bidirectional subscription: one long-lived stream carrying
group and welcome messages, mutated in place (no reconnect on membership
change) and kept alive with WebSocket-style ping/pong. Native-only —
gRPC-Web transports cannot speak full-duplex, so browsers stay on
XmtpMlsStreamswith a client-side watchdog. - Xmtp
MlsStreams - Represents the backend API required for an MLS Delivery Service to be compatible with XMTP streaming
Type Aliases§
- Arced
Xmtp Api - A type-erased version of the Xntp Api in a
Arc - Boxed
GroupS - Boxed
IncomingS - Owned transport events. Durable receipt remains the caller’s responsibility.
- Boxed
SubscribeS - Boxed
WelcomeS - Boxed
Xmtp Api - A type-erased version of the Xmtp Api in a
Box