Skip to content

Conversation

thomaseizinger
Copy link
Member

No description provided.

@thomaseizinger thomaseizinger force-pushed the refactor/update-timers-at branch 4 times, most recently from 1a5d36a to 213d0e4 Compare January 15, 2025 15:23
@thomaseizinger thomaseizinger force-pushed the refactor/update-timers-at branch from 213d0e4 to 7674b90 Compare January 21, 2025 04:20
github-merge-queue bot pushed a commit that referenced this pull request Jun 16, 2025
At present, it is up to the host app how often it calls
`update_timers_at`. Once a second should be enough but ideally, a `Tunn`
just exposes when the next internal timer fires. This is being tackled
more generally in #61. In order to ensure we send keep-alive messages in
time, we incorporate `want_passive_keepalive_at` into the
`next_timer_update` into it.
@thomaseizinger thomaseizinger force-pushed the refactor/update-timers-at branch from 7674b90 to 33edc5f Compare July 15, 2025 12:25
@thomaseizinger thomaseizinger force-pushed the refactor/update-timers-at branch from 33edc5f to 01d1757 Compare July 15, 2025 12:31
@thomaseizinger thomaseizinger force-pushed the refactor/update-timers-at branch from 01d1757 to 533419a Compare July 15, 2025 12:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant