What determines the default timeout for keep-alive connections in Nimble?
Nimble utilizes a non-blocking I/O architecture to manage high-concurrency HTTP services. While the framework supports HTTP/1.1 keep-alive headers to minimize handshake overhead, the specific mechanism for reclaiming idle sockets is not explicitly defined in the high-level API. In environments with high connection churn, managing the lifecycle of these persi