Fetch Hyper

Hyper-based HTTP transport.

Internal implementation detail

This crate is an internal implementation detail of the SDK. It is not part of the public API surface and must not be re-exported from any other crate. Consumers should depend on the higher-level SDK crates instead of taking a direct dependency on fetch_hyper, and SDK crates that do depend on it must keep its types out of their own public APIs (no pub use, no types appearing in public function signatures, trait bounds, or associated types).

No stability guarantees are offered: items may be added, renamed, removed, or have their semantics changed in any release — including patch releases — without notice.

Narrow scope: just the transport that issues HTTP/1.1 or HTTP/2 requests over TLS (or plain-text). No higher-level pipeline, retry, caching, etc.

The entry points are:

• HyperTransportBuilder: generic over a user-supplied Connect service. Exposes setters for the few knobs driving our own logic plus a configure_hyper escape hatch for hyper’s own builder.
• HyperTransport: the type-erased RequestHandler produced by HyperTransportBuilder::build.

The runtime is supplied entirely by the caller via an anyspawn::Spawner together with any service implementing Connect.