From 051f6386c294b55d151de6aa895832cf91957baa Mon Sep 17 00:00:00 2001 From: fewensa Date: Wed, 2 Sep 2026 04:31:05 +0800 Subject: [PATCH] docs(rttp): clarify one-dependency compatibility facade use codeon: version: 1 authority: FWN-225 description: |- Add a concise sentence to `crates/rttp/README.md` explaining that applications wanting a single dependency for both client and server entry points can use the `rttp` compatibility facade. FWN-225 --- crates/rttp/README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/crates/rttp/README.md b/crates/rttp/README.md index 9cb2a441..a21d5ffa 100644 --- a/crates/rttp/README.md +++ b/crates/rttp/README.md @@ -10,6 +10,9 @@ no server loop, event loop, connection pooling, cache, retry, or status-policy engine of its own, and all bounded behavior and metadata-only helpers remain in the underlying `rttp_client` and `rttp-server` crates. +Applications that want one dependency for both client and server entry points +can use this compatibility facade. + ## Server Create a listener with `rttp::Http::server` or call `HttpServer::bind` directly.