Crate kerniq_runtime 

Server lifecycle for Kerniq Server, built on Tokio and Hyper.

• server — the accept loop with connection limits and bounded graceful drain,
• Shutdown / os_signal — shutdown coordination,
• BackgroundTasks — tasks tied to the server lifecycle,
• runtime — the rules for who owns the Tokio runtime.

Kerniq does not implement an executor or an HTTP protocol: Tokio and Hyper do that work.

Re-exports

pub use server::ServeOptions;

pub use server::bind;

pub use server::serve;

Modules

runtime

Tokio runtime ownership.

server

The HTTP accept loop.

Structs

BackgroundTasks

Spawns and tracks background tasks tied to the server lifecycle.

Shutdown

A cloneable handle used to request and observe server shutdown.

Functions

os_signal

Completes when the process receives Ctrl+C (SIGINT) or, on Unix, SIGTERM.