mirror of
https://github.com/logos-messaging/libchat.git
synced 2026-06-30 21:20:09 +00:00
The client, not the app, now drives the transport; events are delivered asynchronously, per ADR 0001. - ChatClient owns Arc<Mutex<Core>> + a worker thread. - The worker select!s over the inbound and shutdown channels; Drop joins it. Outbound runs on the caller's thread. - A single Transport (DeliveryService + inbound()) owns both directions of the boundary, so the client takes one transport rather than a (delivery, inbound) pair. InProcessDelivery::new, CDelivery, and chat-cli's transports implement it. - FFI replaces client_receive with client_push_inbound + client_poll_events. - chat-cli drains Receiver<Event>; inbound and event channels are both crossbeam. - Corrects ADR 0001's inbound sequence to push — the worker parks on select!, it never polls.
20 lines
604 B
Rust
20 lines
604 B
Rust
mod client;
|
|
mod delivery_in_process;
|
|
mod errors;
|
|
mod event;
|
|
|
|
pub use client::{ChatClient, Transport};
|
|
pub use delivery_in_process::{InProcessDelivery, MessageBus};
|
|
pub use errors::ClientError;
|
|
pub use event::Event;
|
|
|
|
// Re-export types callers need to interact with ChatClient.
|
|
pub use libchat::{
|
|
AddressedEnvelope, ConversationClass, ConversationId, DeliveryService, RegistrationService,
|
|
StorageConfig,
|
|
};
|
|
|
|
// Re-export bundled registry implementations so callers can pick one without
|
|
// pulling in `components` directly.
|
|
pub use components::{EphemeralRegistry, HttpRegistry, HttpRegistryError};
|