mirror of https://github.com/logos-messaging/libchat.git synced 2026-06-28 03:59:27 +00:00

History

feat(client): add threaded transport polling (#125 )

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.

2026-06-11 10:08:07 +02:00

main.rs

feat(client): add threaded transport polling (#125 )

2026-06-11 10:08:07 +02:00

README.md

feat: implement Client crate and C FFI bindings (#73 )

2026-04-08 23:15:48 +02:00

README.md

message-exchange

An example Rust application built on top of crates/client.

It demonstrates that creating a working chat client in pure Rust is trivial: depend on crates/client, pick a DeliveryService implementation (here the in-memory InProcessDelivery shipped with the crate), and wire up ChatClient. No boilerplate, no FFI.

Running

cargo run --example message-exchange

The binary performs a message exchange entirely in-process and prints the exchanged messages to stdout.