Module jsonrpc 

Routing a decoded JSON-RPC message to a method, without naming one.

The seam

MethodTable is the boundary between “this is a well-formed JSON-RPC message naming tools/call” and “run the tool handler”. The first half is finished here, for every protocol at once, because it is the same work whatever the method is. The second half belongs to a protocol module and is T12’s.

Nothing in this module names an MCP method. A2A and ACP register their own tables under adapters the same way MCP does, which is the property the project’s protocol-neutral rule asks for and the reason a later task can add a protocol without a refactor.

Two ports, and why they are not one

FrameSource is the inbound edge — a stream of whole frames — and it is declared here because the loop that reads a frame and routes it is this module’s consumer. The outbound edge is FrameSink, which sits with the session engine that consumes it instead. Same direction of travel, different consumer, different module: a trait that both read and wrote would make every implementor answer for both, and a replay source only reads at all.

Re-exports

pub use batch::AllowBatching;

pub use batch::BatchPolicy;

pub use batch::DenyBatching;

pub use batch::ProfileBatching;

pub use document::RequestError;

pub use document::notification_document;

pub use document::reply_result;

pub use document::request_document;

pub use frame_source::DynFrameSource;

pub use frame_source::FrameSource;

pub use frame_source::SourceError;

pub use router::MethodTable;

pub use router::ReplyPayload;

pub use router::RouteError;

pub use router::Routed;

pub use router::RoutedFrame;

pub use router::RoutedMessage;

pub use router::route_frame;

pub use router::route_one;

Modules

batch

Whether this session accepts a batch frame at all.

document

The documents a client writes, and the one it reads back.

frame_source

The inbound edge: a stream of whole frames from a peer.

router

Turning a decoded envelope into a method to dispatch, without naming one.