Development edition · 16 November 2026. Commands using repository paths, Make targets or sample projects require access to the Quinzee source checkout. No public installer is available. Examples use disposable local environments.
3. HTTP library and asynchronous execution
The transport library supports synchronous handlers and asynchronous completion.
server owns an implementation with validated immutable configuration, a listener
I/O context, connection registry, acceptor and lifecycle timers. Lifecycle calls
from its own I/O thread are forbidden; a handler cannot safely destroy its server.
| Public contract | Purpose |
|---|---|
request_handler / async_request_handler |
Immediate response or deferred response_completion |
request_executor |
Bounded worker/queue adapter with active, queued and rejected statistics |
request, response |
Owned protocol values, headers, cancellation and body access |
body_file |
File-backed body lifetime used for large streamed transfers |
server_config, tls_config |
Bounded transport options and TLS certificate configuration |
exchange_statistics / observe_exchange |
Optional completion accounting without Azure dependencies |
error, log_sink |
Lifecycle errors and optional thread-safe logging |
The cloud composes eight request workers with a queue of 64. Saturation rejects work explicitly; it must not create unbounded threads or block the listener's I/O thread. Completion is delivered back to the appropriate connection executor. Cancellation and handler deadlines prevent abandoned connections from retaining work indefinitely; application code must still cooperate with cancellation.
Request/response validation rejects malformed headers and application-controlled framing. Keep-alive, HEAD semantics, chunking and socket writes remain transport responsibilities. Large body handlers use the file-backed API rather than converting every request into an in-memory string.
Read the public headers in include/http/ (source checkout required) and the
application transfer design (source checkout required).
integration.http_stream covers large-body lifetime, backpressure and completion
accounting; ordinary HTTP/TLS tests cover connection and protocol failures.