Enum ControlEvent 

pub enum ControlEvent {
    Connected {
        connection_id: u64,
        fd: RawFd,
        writer: BlockingFrameWriter<Box<dyn Write + Send>>,
    },
    Disconnected {
        connection_id: u64,
    },
    PipelineBusy {
        connection_id: u64,
    },
}

Control-plane event the accept loop, reader, and response stage exchange. Transport-agnostic — the payload is a socket fd + writer, not an app event — so both build modes refer to the same type.

Variants

Connected

Fields

connection_id: u64

fd: RawFd

writer: BlockingFrameWriter<Box<dyn Write + Send>>

Disconnected

Fields

connection_id: u64

PipelineBusy

Reader → response: the input pipeline was full when this connection’s frame arrived; deliver a ServerBusy notice through the normal egress path. Routed through the response stage so exactly one thread ever writes a client socket — a reader-side send could land between the two halves of a partially-flushed response frame and permanently desync the client’s length-prefix framing (2026-08 io_uring audit, review finding F3).

Fields

connection_id: u64