Skip to content

fix: reset Remoter idle deadlines and refresh TLS activity - #168

Open
kentbull wants to merge 3 commits into
ioflo:mainfrom
kentbull:fix/remoter-idle-timeout-refresh
Open

fix: reset Remoter idle deadlines and refresh TLS activity#168
kentbull wants to merge 3 commits into
ioflo:mainfrom
kentbull:fix/remoter-idle-timeout-refresh

Conversation

@kentbull

@kentbull kentbull commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Reset Remoter idle deadlines from current scheduler tyme with Tymer.start().
  • Refresh RemoterTls after successful nonempty receives and nonzero sends.
  • Preserve untimed Remoters and avoid refreshing blocked, empty, or failed I/O.

This fixes both idle-timer defects: plain TCP accumulated time from the previous deadline, while successful TLS traffic did not refresh inactivity. It complements #164, which propagates the Server timeout to accepted Remoters.

Closes #169
Closes #170

Use Tymer.start() so successful I/O refreshes inactivity from the current scheduler tyme instead of accumulating duration from the previous stop. Cover repeated refreshes and recovery after expiration.
Skip idle timer reset until a Remoter has an injected scheduler tyme. This preserves untimed TCP and HTTP use while Tymer.start() governs configured inactivity.
RemoterTls overrides the plain TCP receive and send paths but omitted their activity refresh. Mirror Remoter so nonempty reads and nonzero writes reset configured inactivity without refreshing blocked or failed I/O.

Extend the existing TLS integration test to verify both directions. This fixes ioflo#170 and relies on the current-tyme refresh semantics introduced earlier in this branch.
@kentbull kentbull changed the title fix: reset Remoter idle timeout from current tyme fix: reset Remoter idle deadlines and refresh TLS activity Aug 29, 2026
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.

RemoterTls does not refresh idle timeout after successful I/O Remoter.refresh accumulates idle timeout from the previous deadline

1 participant