Files and Streams

A streamed reply is chunked for HTTP/1.1 peers, keeps identity framing when its headers declare Content-Length, and is delimited by the close for HTTP/1.0 peers; a chunk reports ucall_status_would_block_k while the socket lags too far behind. Vectored replies and stream chunks take reply parts: bytes, a range of a file descriptor the caller keeps open until the outcome is final, or a range of a path opened beneath one of the interface’s reply_directories. The event loop opens files with O_DIRECT, refusing caller descriptors without it, and reads aligned extents itself before sending the requested slice. Replies leave through zero-copy sends, so a connection closes only once the kernel let go of what it sent, and resets a peer that stops acknowledging by the linger deadline. A reply with file or path parts publishes its outcome as ucall_status_deferred_k, then success once they are sent, or the cause; a refusal before the head becomes 404 or 416, and a failure after it resets the connection.