std only.Expand description
Phantom Protocol - Fallback State Machine
A degrade/heal state machine over three abstract transport “modes”
(Turbo → Reliable → Stealth): on repeated connection failures it walks one
step toward the most-robust mode, and probes back up to the best mode when the
path heals. The mode names predate the PhantomUDP rewrite — the concrete
KCP / TCP / FakeTLS legs they referred to are gone (PhantomUDP is now the only
production transport, with TCP/WebSocket/WASI/Embedded/MimicTls byte-pipes).
Vestigial. The machine is still constructed inside Session (held behind
#[allow(dead_code)]) but no longer steers a live transport — the project does
single-path connection migration, not transport-mode switching. The logic and
tests are kept intact in case mode-switching is rewired against the current
transports; treat the Turbo/Reliable/Stealth names as opaque tiers, not
as the retired legs.
Structs§
- Fallback
Metrics - Fallback
State Machine - Fallback state machine
- Fallback
Trigger - Conditions that trigger a fallback
Enums§
- Transport
Mode - Abstract transport-robustness tiers, most→least performant. The names are historical (they once mapped to the retired KCP / TCP / FakeTLS legs) and are now opaque ordering labels for the degrade/heal walk, not concrete transports.