Expand description
Backend client handler that bridges server notifications to upstream peers.
Two isolation modes share one BackendNotificationBridge type so
crate::proxy_handler::BackendRunningService stays a single concrete type:
- Shared (
NotifyTarget::Shared): one backend, fan-out / progress·task routing viaUpstreamPeerRegistry(stdio proxy). - Per-session (
NotifyTarget::Session): one backend connection owns one upstreamPeer; notifications are 1:1 (URL proxy).
Structs§
- Backend
Notification Bridge - Client-side handler used when the proxy connects to a backend MCP server.
- Progress
Route Guard - RAII guard that unregisters a progress route when dropped (after a short grace).
- Upstream
Peer Registry - Registry of upstream session peers that should receive backend notifications.
- Upstream
Peer Slot - Slot for the single upstream peer in per-session isolation mode.
Enums§
- Notify
Target - How backend notifications are delivered to upstream Streamable HTTP sessions.
Constants§
- PROGRESS_
ROUTE_ GRACE - Delay before unregistering a progress route after the owning request finishes.
Functions§
- default_
backend_ client_ info - Default
ClientInfofor proxy→backend handshake (enables task notifications).