Expand description
Minimal HTTP server for RedDB management and remote access.
Re-exports§
pub use self::http_limits::HttpLimitsCliInput;pub use self::http_limits::HttpLimitsResolved;pub use self::http_limits::DEFAULT_HANDLER_TIMEOUT_MS;pub use self::http_limits::DEFAULT_RETRY_AFTER_SECS;
Modules§
- handlers_
admin - Lifecycle / admin HTTP endpoints (PLAN.md Phase 1).
- header_
escape_ guard HeaderEscapeGuard— typed boundary guard for HTTP response header values.- http_
connection_ limiter - Bounded handler-thread admission for the clear-text HTTP accept loop.
- http_
handler_ metrics - Prometheus metrics for the HTTP handler-thread pool.
- http_
limits - Resolution of the three HTTP handler-pool knobs (issue #574 slice 5).
- ingest_
pipeline - JSON-first ingest pipeline — autodetects JSON-array bodies,
NDJSON streams, and envelope-style payloads, then hands the
rows over to the storage layer as a
Vec<HashMap<String, Value>>. - output_
stream - Output streaming primitives for issue #760 (PRD #759 / ADR 0029) — the “shim slice” of bidirectional streaming.
- tls
- HTTP TLS termination for the embedded HTTP server.
Structs§
- RedDB
Server - Server
Options - Server
Replication State - Replication state exposed to the HTTP server.
Enums§
- Server
Surface - PLAN.md Phase 6.2 — endpoint segregation. A given HTTP listener
can serve either every public surface (
Public, default) or a restricted slice (AdminOnly,MetricsOnly). The route filter at the top ofroute()consults this so a port bound only to loopback for admin work won’t accidentally hand out DML.