Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for client initiated drain #606

Closed
wants to merge 2 commits into from

Conversation

nidhijaju
Copy link
Member

@nidhijaju nidhijaju commented Jun 19, 2024

Fixes #436.

I'm not totally sure what "draining" is doing here, if we're not blocking new stream creations or cleaning up the transport object, but I think this is what was discussed on the issue.


Preview | Diff

@nidhijaju nidhijaju requested review from vasilvv and jan-ivar June 19, 2024 03:41
1. If |transport|.{{[[State]]}} is `"closed"` or `"failed"`, [=throw=] an {{InvalidStateError}}
and abort these steps.
1. Set |transport|.{{[[State]]}} to `"draining"`.
1. Let |draining| be |transport|.{{[[Draining]]}}.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The existing definitions of [[Draining]] and concept of draining are now incomplete as they specifically only mention that they describe server-initiated drain. These need to be updated to include that this state can be initiated client-side.

@jan-ivar
Copy link
Member

jan-ivar commented Jul 2, 2024

@jan-ivar
Copy link
Member

jan-ivar commented Jul 30, 2024

Meeting:

  • Not hearing any support in this meeting for this feature
  • Also no clear answer from IETF
  • Closing due to lack of interest

@jan-ivar jan-ivar closed this Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Client initiated drain
2 participants