Keepalive: notice a connection that hangs without an error

littlefox commented

2026-10-17 21:23:09 +00:00

Owner

Follow-up to #52. Reconnecting starts when the connection's driver ends (an error or a close). A connection can also hang silently (a laptop waking on another network, a NAT dropping state): nothing arrives, and calls wait forever.

What:

A cheap call (get-time) every minute or so while idle; no answer within ~20 s means the connection is dead.
kom-client needs a way to close a connection from our side (Client::close or the driver ending on request), so the reconnect logic in #52 takes over.
Also on the web: the page coming back to the foreground (visibilitychange) checks at once.

Done when:

A test where the relay stops forwarding (but keeps the socket open) ends in a reconnect.

Follow-up to #52. Reconnecting starts when the connection's driver ends (an error or a close). A connection can also hang silently (a laptop waking on another network, a NAT dropping state): nothing arrives, and calls wait forever. What: - A cheap call (get-time) every minute or so while idle; no answer within ~20 s means the connection is dead. - kom-client needs a way to close a connection from our side (Client::close or the driver ending on request), so the reconnect logic in #52 takes over. - Also on the web: the page coming back to the foreground (visibilitychange) checks at once. Done when: - A test where the relay stops forwarding (but keeps the socket open) ends in a reconnect.

littlefox added this to the 0.2: Feels like an app milestone

2026-10-17 21:23:09 +00:00

littlefox added the

kind/feature

area/protocol

labels

2026-10-17 21:23:09 +00:00

littlefox referenced this issue from a commit

2026-10-17 21:41:20 +00:00

Reconnect by itself when the connection drops, and go back there

littlefox referenced this issue

2026-10-17 21:41:20 +00:00

0.2: errors, command palette, first-run tour, reconnecting #84

littlefox referenced this issue

2026-10-17 22:51:58 +00:00

Reconnect quietly when the connection drops #52

littlefox referenced this issue from a pull request that will close it,

2026-10-17 23:01:07 +00:00

0.2: stay logged in, soak test, installable web app, keepalive #88

littlefox closed this issue

2026-10-18 00:35:15 +00:00

littlefox referenced this issue from a commit

2026-10-18 00:35:16 +00:00

Keepalive: notice a connection that hangs without an error

littlefox commented

2026-10-18 00:55:58 +00:00

Author

Owner

Merged in #88. Client::close(); get-time every 45 s and when the page becomes visible; no answer in 20 s closes and reconnects. Unit test with a silent transport; reconnect.spec.ts makes the open socket pass nothing and checks the reconnect.

littlefox referenced this issue

2026-10-21 19:08:09 +00:00

Idle cost: timers and global signals that redraw while nothing happens #233

Rows
Columns

Keepalive: notice a connection that hangs without an error #81