Struct WsChannel 

pub struct WsChannel {
    pub write: Mutex<WsSink>,
    pub pending: Mutex<HashMap<String, Sender<ToolExecuteResponse>>>,
    pub active_actions: Mutex<HashMap<String, String>>,
    pub next_id: AtomicU64,
}

Shared write half of the WebSocket, plus pending callback channels. write is type-erased via WsSink so the dispatcher can run against any transport-specific WebSocketStream (TCP or UDS today; axum-bridged in future) without templatizing every consumer.

Fields

write: Mutex<WsSink>

pending: Mutex<HashMap<String, Sender<ToolExecuteResponse>>>

Pending tool execution callbacks: request_id → oneshot sender

active_actions: Mutex<HashMap<String, String>>

Body-free correlation for active callbacks. A session owns at most one active run, so every entry belongs to that run while its lifecycle guard is held by proposal execution.

next_id: AtomicU64

Implementations

impl WsChannel

pub fn next_request_id(&self) -> String

Trait Implementations

impl EventSubscriber for WsChannel

A WS connection is a host event sink (#418): HostState broadcasts host.event frames to subscribers through this trait, so it never has to know about the concrete WsChannel / tungstenite types.

fn send_text<'life0, 'async_trait>( &'life0 self, json: String, ) -> Pin<Box<dyn Future<Output = ()> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait,

Send a pre-serialized JSON-RPC frame. Best-effort: a wedged/closed socket is reaped by the next unsubscribe, not surfaced as an error here.