RaftTransport
The messaging seam between the Raft engine and any underlying network layer.
RaftTransport decouples the engine from the wire — the same engine code runs over WebSocket (SeamRaftTransport), in-process channels (tests), or any other point-to-point fabric. Implement this interface to plug in a custom transport.
Reachability vs. membership. peers reflects which nodes the transport can currently reach, not which nodes are configured voters. A node may be a configured voter but momentarily absent from peers (network partition), or absent from the cluster config entirely (unknown peer). The engine handles both cases.
Single collection. incoming is a hot flow; collect it once. The engine calls RaftTransport.incoming exactly once per RaftNode lifetime.
Inheritors
Properties
Hot flow of inbound RaftEnvelopes from other cluster members.
The maximum number of bytes a single sendTo payload can carry, or null if effectively unbounded (e.g. WebSocket). Fabrics with hard framing limits (e.g. ~32 KiB on some LAN radios) return that limit so kuilt-raft can size InstallSnapshot chunks to fit. Defaulted — existing transports need no change.
This node's own stable identifier. Must match its entry in ClusterConfig.