libchat/crates/generic-chat/examples/message-exchange/README.md

# message-exchange

An example Rust application built on top of [`crates/generic-chat`](../../).

It demonstrates that creating a working chat client in pure Rust is trivial: depend on
`crates/generic-chat`, 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.
feat: implement Client crate and C FFI bindings (#73) Implement a `client` crate that wraps the `libchat` context behind a simple `ChatClient<D>` API. The delivery strategy is pluggable via a `DeliveryService` trait, with two implementations provided: - `InProcessDelivery` — shared `MessageBus` for single-process tests - `CDelivery` — C function-pointer callback for the FFI layer Add a `client-ffi` crate that exposes the client as a C API via `safer-ffi`. A `generate-headers` binary produces the companion C header. Include two runnable examples: - `examples/in-process` — Alice/Bob exchange using in-process delivery - `examples/c-ffi` — same exchange written entirely in C; smoketested under valgrind (to catch memory leaks) in CI iterates: #71 2026-04-08 23:15:48 +02:00			`# message-exchange`

feat: separate embedded logos client (#166) * feat: separate embedded p2p delievery to its own crate * feat: separate p2p config in its own crate * chore: split embed module * chore: refactor registry config * feat: split logos chat crate * chore: refactor 2026-07-09 15:12:58 +08:00			An example Rust application built on top of [`crates/generic-chat`](../../).
feat: implement Client crate and C FFI bindings (#73) Implement a `client` crate that wraps the `libchat` context behind a simple `ChatClient<D>` API. The delivery strategy is pluggable via a `DeliveryService` trait, with two implementations provided: - `InProcessDelivery` — shared `MessageBus` for single-process tests - `CDelivery` — C function-pointer callback for the FFI layer Add a `client-ffi` crate that exposes the client as a C API via `safer-ffi`. A `generate-headers` binary produces the companion C header. Include two runnable examples: - `examples/in-process` — Alice/Bob exchange using in-process delivery - `examples/c-ffi` — same exchange written entirely in C; smoketested under valgrind (to catch memory leaks) in CI iterates: #71 2026-04-08 23:15:48 +02:00
			`It demonstrates that creating a working chat client in pure Rust is trivial: depend on`
feat: separate embedded logos client (#166) * feat: separate embedded p2p delievery to its own crate * feat: separate p2p config in its own crate * chore: split embed module * chore: refactor registry config * feat: split logos chat crate * chore: refactor 2026-07-09 15:12:58 +08:00			`crates/generic-chat`, pick a `DeliveryService` implementation (here the in-memory
feat: implement Client crate and C FFI bindings (#73) Implement a `client` crate that wraps the `libchat` context behind a simple `ChatClient<D>` API. The delivery strategy is pluggable via a `DeliveryService` trait, with two implementations provided: - `InProcessDelivery` — shared `MessageBus` for single-process tests - `CDelivery` — C function-pointer callback for the FFI layer Add a `client-ffi` crate that exposes the client as a C API via `safer-ffi`. A `generate-headers` binary produces the companion C header. Include two runnable examples: - `examples/in-process` — Alice/Bob exchange using in-process delivery - `examples/c-ffi` — same exchange written entirely in C; smoketested under valgrind (to catch memory leaks) in CI iterates: #71 2026-04-08 23:15:48 +02:00			`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.`