Expand description
Completion-native HTTP building blocks for Karmaio.
Message metadata uses the standard http types. Vakya targets Karmaio’s
local execution and owned-buffer model, without requiring Send or Sync
on application work.
§Features
No features are enabled by default. client and server each enable
http1. tls adds supplied-TLS-stream integration without selecting a role,
crypto provider, or trust store. tracing observes lifecycle events, and
full enables both roles, TLS, and tracing.
§Execution and ownership
Applications supply established transports and drive the returned connection
future concurrently with their service or client operations. Vakya does not
spawn a driver, establish TLS, resolve names, pool connections, or retry
accepted requests. See the client and server modules for role entry points.
body::Body uses native async methods and Karmaio-owned buffers. body::Incoming
applies bounded demand; dropping it abandons unfinished receiving. Explicit
shutdown and timeout paths settle retained I/O. Dropping a driver preserves
runtime buffer safety without promising graceful flush or recycling callbacks.
HTTP/1 is implemented; HTTP/2 and HTTP/3 are outside the current API.
Re-exports§
pub use http::HeaderMap;pub use http::HeaderName;pub use http::HeaderValue;pub use http::Method;pub use http::Request;pub use http::Response;pub use http::StatusCode;pub use http::Uri;pub use http::Version;
Modules§
- body
- Completion-native streaming bodies and payload metadata.
- client
client - Low-level HTTP clients over established Karmaio transports.
- connection
http1 - Controls and outcomes of a caller-driven HTTP connection.
- error
- Public error categories for HTTP and connection operations.
- server
server - Low-level HTTP servers over established Karmaio transports.
- service
- Native asynchronous service composition.
- tls
tls - TLS metadata for connections over established Karmaio TLS streams.
- upgrade
http1 - Typed transport ownership after an HTTP protocol switch or CONNECT tunnel.