Struct ServerRegistry 

pub struct ServerRegistry { /* private fields */ }

Process-global registry mapping (host, port) → running Axum server handle.

Implementations

impl ServerRegistry

pub fn global() -> &'static Self

Returns the global singleton.

pub async fn get_or_spawn( &'static self, host: &str, port: u16, max_request_body: usize, max_response_body: usize, max_inflight_requests: usize, runtime: Arc<dyn RuntimeObservability>, route_id: String, tls_config: Option<ServerTlsConfig>, ) -> Result<HttpRouteRegistry, CamelError>

Returns route registry for port, spawning new Axum server if none is running on that port yet.

pub async fn get_or_spawn_with_listener( &'static self, listener: TcpListener, max_request_body: usize, max_response_body: usize, max_inflight_requests: usize, runtime: Arc<dyn RuntimeObservability>, route_id: String, tls_config: Option<ServerTlsConfig>, ) -> Result<HttpRouteRegistry, CamelError>

Like ServerRegistry::get_or_spawn, but serves listener instead of binding host:port. The registry key is derived from the listener’s actual local address, so callers must query that port afterwards. If an entry for the key already holds a live server, the same compatibility checks as get_or_spawn apply and the entry is reused; the passed listener is simply dropped.

pub async fn stage_listener( &'static self, listener: TcpListener, ) -> Result<(), CamelError>

Stage a pre-bound listener so the next get_or_spawn for its (ip, port) key serves this socket instead of binding a new one.

The staged listener is consumed by exactly one spawn: the exact-key get_or_spawn takes it under the registry lock, eliminating the bind window between a port probe and server startup (itest-bound-ports).

pub fn bound_addr(&'static self, host: &str, port: u16) -> Option<SocketAddr>

Returns the bound address of the live server entry for (host, port), if one is initialized.

pub async fn unregister(&self, host: &str, port: u16)

Unregister one consumer from a server. HTTP servers are process-lifetime: the server stays in the registry for potential restart. Path deregistration happens separately in the consumer’s cleanup.