joule-moq-relay: each end of a WebSocket session pings the other every 30 s #513

Merged

dcharlot merged 1 commit from wai/relay-ws-ping into main 2026-10-27 16:14:29 -04:00

Conversation 0 Commits 1 Files changed 3 +78 -5

dcharlot commented 2026-10-27 14:40:05 -04:00

Owner

Copy link

The edge relay's link to its home relay runs over wss:// through a tunnel that closes connections it sees idle. With no one watching, the link carried nothing, so the tunnel cut it every two minutes. Each time the edge redialled within two seconds: the edge's journal showed an end-and-reopen pair every ~126 s, and the home relay logged a new hop link at each one.

The change: each end of a WebSocket session (relay accepting, or relay dialling an upstream) sends a WebSocket ping (RFC 6455 §5.5.2) every 30 s while the session lasts. The peer's WebSocket answers with a pong, so a front between them sees traffic both ways. The MOQT session is unaffected: the receiver already ignored non-binary messages, and the library answers pings.

• transport/websocket.rs: PING_EVERY (30 s); session pings at it, and session_pinging takes the interval. The sender is shared with the ping task, which holds only a weak reference, so the pings stop when the session's sender is dropped or a ping cannot be sent.
• README.md: the binding gains step 8, "Keeping alive".

Checks (Framework box):

• cargo test --locked -p joule-moq-relay: every test passes, including the new an_idle_session_pings_its_peer (three pings at a 50 ms interval).
• Falsified: with the ping loop's tick replaced by break, the new test fails ("0 arrived"); restored.
• cargo clippy -p joule-moq-relay --all-targets --no-deps -D warnings: nothing in the changed files. The host's newer clippy flags server.rs:182 (a large Err variant), which this change does not touch; CI's pinned clippy passes it on main.
• The public-name, comparative-prose and vanity-metric checks are clean.

Deploy note: the edge (ash-1) needs the rebuilt relay for the pings on its upstream link; the home relay gains them for the sessions it accepts.

🤖 Generated with Claude Code

The edge relay's link to its home relay runs over `wss://` through a tunnel that closes connections it sees idle. With no one watching, the link carried nothing, so the tunnel cut it every two minutes. Each time the edge redialled within two seconds: the edge's journal showed an end-and-reopen pair every ~126 s, and the home relay logged a new hop link at each one. **The change:** each end of a WebSocket session (relay accepting, or relay dialling an upstream) sends a WebSocket ping (RFC 6455 §5.5.2) every 30 s while the session lasts. The peer's WebSocket answers with a pong, so a front between them sees traffic both ways. The MOQT session is unaffected: the receiver already ignored non-binary messages, and the library answers pings. - `transport/websocket.rs`: `PING_EVERY` (30 s); `session` pings at it, and `session_pinging` takes the interval. The sender is shared with the ping task, which holds only a weak reference, so the pings stop when the session's sender is dropped or a ping cannot be sent. - `README.md`: the binding gains step 8, "Keeping alive". **Checks (Framework box):** - `cargo test --locked -p joule-moq-relay`: every test passes, including the new `an_idle_session_pings_its_peer` (three pings at a 50 ms interval). - **Falsified:** with the ping loop's tick replaced by `break`, the new test fails ("0 arrived"); restored. - `cargo clippy -p joule-moq-relay --all-targets --no-deps -D warnings`: nothing in the changed files. The host's newer clippy flags `server.rs:182` (a large `Err` variant), which this change does not touch; CI's pinned clippy passes it on main. - The public-name, comparative-prose and vanity-metric checks are clean. **Deploy note:** the edge (ash-1) needs the rebuilt relay for the pings on its upstream link; the home relay gains them for the sessions it accepts. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

dcharlot added 1 commit 2026-10-27 14:40:05 -04:00

joule-moq-relay: each end of a WebSocket session pings the other every 30 s ... 372a3e953d

The edge relay's link to its upstream runs over wss through a tunnel that
closes a connection it sees idle. With no one watching, the link carried
nothing, and the tunnel cut it every two minutes; the edge redialled within
two seconds each time. Each end now sends a WebSocket ping (RFC 6455
§5.5.2) every 30 s while the session lasts, and the peer's WebSocket
answers with a pong. The binding's README gains the step.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

dcharlot merged commit c19688a555 into main 2026-10-27 16:14:29 -04:00

dcharlot referenced this pull request from a commit 2026-10-27 16:14:30 -04:00

Merge pull request 'joule-moq-relay: each end of a WebSocket session pings the other every 30 s' (#513) from wai/relay-ws-ping into main

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

Transaction-Science/open-standards!513

No description provided.