Talon/chat_grid
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

net: prioritize close-event reconnect with 2s delay and 3 retry cap

Browse Source
This commit is contained in:
Jage9
2026-02-22 18:47:09 -05:00
parent d5dbb8289a
commit 7e3553dbde
4 changed files with 41 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/runtime-flow.md
View File

@@ -47,8 +47,10 @@ Core incoming message effects:
## Stale Connection Recovery
- While running, client sends heartbeat `ping` every 10 seconds.
- If one heartbeat `pong` is missed (10-second interval), client auto-reconnects.
- If websocket closes unexpectedly, client starts reconnect flow immediately.
- While running, client also sends heartbeat `ping` every 10 seconds (fallback for silent half-open cases).
- If one heartbeat `pong` is missed (10-second interval), client starts reconnect flow.
- Reconnect flow waits 2 seconds and retries up to 3 times.
- If reconnect lands on a different `welcome.serverInfo.instanceId`, client announces server restart.
- Connect/reconnect status message is emitted from `welcome` and includes server version.