Skip to content

Settle HTTP responses before reconnecting after cutoff - #24

Merged
kentbull merged 1 commit into
release/v0.6.20from
fix/http-client-cutoff-settlement-v0.6.20
Aug 29, 2026
Merged

kentbull merged 1 commit into
release/v0.6.20from
fix/http-client-cutoff-settlement-v0.6.20

Conversation

@kentbull

@kentbull kentbull commented Aug 29, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • settle the old response generation before reopening after connector cutoff
  • preserve valid close-delimited responses and expose truncated framed responses as errors
  • parse accepted SSE events before applying their reconnect interval
  • clear residual old-generation bytes after settlement and defer new connection work

Why

EOF belongs to the transport generation that observed it. Reopening first resets the response parser before it can classify the old bytes, collapsing three different outcomes: a valid close-delimited response, a truncated framed response, and an SSE stream whose final accepted event changes reconnect timing. Settling the old parser before reconnect preserves message framing, failure truth, and application-visible SSE state.

Service the old Respondent while its EOF remains latched, package either its close-delimited success or framed failure, and only then clear residual receive bytes and reopen the connector.

Preserve accepted SSE events and their retry interval, and defer work on the new connection until a later recurrence. Exercise all paths with real TCP clients, servers, sockets, and accepted Remoters.
@kentbull
kentbull merged commit d260d83 into release/v0.6.20 Aug 29, 2026
6 checks passed
@kentbull
kentbull deleted the fix/http-client-cutoff-settlement-v0.6.20 branch August 29, 2026 15:36
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