📝 docs: WS session expiry settled — stream survives, handshake-only enforcement #205
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/ws-expiry-settled"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The sleep-inhibited rerun settled the question #189 left open. The stream received frames continuously across the boundary (2631 at expiry−4 min → 2749 at expiry+1 min, same ~100–118 frames/300 s cadence, 2761 frames over 2 h 01 m; wall/monotonic clocks matched to ~1 s — no suspend this time). Meanwhile the expired cookie is rejected at every new presentation: REST → 401, fresh WS handshake → HTTP 401.
Consequence recorded: expiry cannot kill a running stream — only a re-handshake (reconnect) needs a fresh cookie. The client's layered design (proactive pre-handshake refresh + reactive 401 fallback) is validated; no mid-stream session keep-alive is needed.
Evidence
pytest= 242 passed,mypyclean.Merge Danger
Door: two-way — documentation only.
Blast Radius: none — no code change; closes the observation deferred by #158/#161.
WIP: 📝 docs: WS session expiry settled — stream survives, handshake-only enforcementto 📝 docs: WS session expiry settled — stream survives, handshake-only enforcement