Module session 

Layer 5: Session — Peer identity, connection lifecycle, message routing.

The PeerRegistry is the central component. It consumes peer discovery events from Layer 3 (NetworkProvider) and manages transport connections from Layer 4 (StreamTransport, [RawTransport]).

Layer rules

• Layer 5 does NOT know what the data means (no namespaces, no envelopes)
• Layer 5 does NOT inspect payloads
• Layer 5 does NOT do peer discovery — it consumes Layer 3 events
• Peers exist because Layer 3 says they exist, NOT because of connections
• Connections are lazy — established on first send()
• Layer 5 does NOT implement any transport protocol — it delegates to Layer 4

Modules

reconnect

Exponential backoff tracker for reconnection attempts.

Structs

IncomingMessage

An incoming message received from a peer via WebSocket.

PeerRegistry

Manages peer state and WebSocket connections.

PeerState

A peer’s state in the session registry.

Enums

PeerEvent

Events emitted by the session layer when peer state changes.

SessionError

Errors from Layer 5 session operations.