Expand description
R2.2 typed-fate wiring: socket facts enter the client unit; policy never exits it.
The binding owns one ClientParticipantAggregate and mediates every real
WebSocket socket open against the client unit’s sealed reconnect machinery:
a socket may open only after a one-use permit has become a
ReconnectInProgressAttempt; open completion is passed as
ReconnectAttemptFate::Connected/ReconnectAttemptFate::Failed;
established loss is passed as EstablishedConnectionTransportFate::Lost;
and a detach-send loss is passed to the typed detach replay fate. The
aggregate — never this binding, never the adapter — decides whether an
attempt, replay, park, refusal, or terminal result exists. A WebSocket
close code, I/O failure, or protocol violation is diagnostic data only and
never selects an aggregate transition.
Structs§
- WebSocket
Authority Binding - Socket-fact conduit into one
ClientParticipantAggregate.
Enums§
- Attempt
Fate Outcome - Outcome of recording an open-completion socket fate.
- Attempt
Fate Refusal - Closed refusal classes for an open-completion fate.
- Detach
Loss Outcome - Outcome of reporting a detach-send transport loss.
- Loss
Record Outcome - Outcome of recording an established-connection loss.
- Loss
Record Refusal - Closed refusal classes for an established-loss report.
- Open
Request Decision - Decision for one open request.
- Open
Request Refusal - Closed refusal classes for an open request.