Skip to content

docs(rttp): clarify one-dependency compatibility facade use #864

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
fewensa merged 1 commit into from
Sep 1, 2026
Merged

docs(rttp): clarify one-dependency compatibility facade use #864

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions crates/rttp/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down