Skip to main content

Module hub

Module hub 

Source
Expand description

The mesh side of the stable inference address in a daemon that owns its mesh connections (collapsed or legacy mode): adverts and forwarded requests travel as control messages on INFER_TOPIC, handed to the hub with the connection’s own PeerCtx.

Everything that decides trust comes from that context, never from the payload: the sender of an advert is ctx.peer_id, the standing of a peer is the grant its connection holds (PeerCtx::grant), and a served request is checked against it by serve_infer. The hub never runs in service mode: there the daemon is handed deliveries as an unverified peer and holds no grant for anyone (see mesh_local_sink), so nothing could be served or ingested safely.

Each forwarded request is one exchange keyed by (peer, id); the exchange is presented to [forward_remote] and serve_infer as a MeshStream, so the forwarding code is the same one the tests drive over in-memory streams.

Structs§

InferHub
Adverts, forwarded requests and their responses between peers.