Expand description
Whether this session accepts a batch frame at all.
§Why this is a port and not a flag
Batching is not a transport setting and it is not a decode setting. It is a
property of the negotiated pair, and it moved once already: 2025-06-18
removed it, and 2026-07-28 is stateless precisely because a stateless
request cannot be correlated without one. So the question is asked against
the session’s FeatureProfile rather than answered once at construction.
Keeping it a trait rather than a bool is what lets A2A and ACP each bring their own answer. A bool would put the default — “batching is fine” — in the JSON-RPC core, and the default is the wrong one: a protocol that never defined batching would silently inherit support for it.
Structs§
- Allow
Batching - Always accept a batch, whatever the profile says.
- Deny
Batching - Refuse every batch.
- Profile
Batching - Batching only when the negotiated pair supports it.
Traits§
- Batch
Policy - Decides whether a batch frame is acceptable in this session.