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

Propagate ChannelShouldQuiesceEvent to child channels #464

Merged
merged 1 commit into from
Sep 18, 2024

Conversation

glbrntt
Copy link
Contributor

@glbrntt glbrntt commented Sep 17, 2024

Motivation:

NIO has a 'ChannelShouldQuiesceEvent' which channels can listen for in order to know when they should quiesce. This is typically used to initiate a graceful shutdown of an HTTP/2 server. However, child channels aren't notified of this event so HTTP/2 servers must keep track of streams separately in order to notify them when the server is quiescing.

Modifications:

  • Propagate the ChannelShouldQuiesceEvent to child channels

Result:

Child channels can watch for ChannelShouldQuiesceEvents

Motivation:

NIO has a 'ChannelShouldQuiesceEvent' which channels can listen for in
order to know when they should quiesce. This is typically used to
initiate a graceful shutdown of an HTTP/2 server. However, child
channels aren't notified of this event so HTTP/2 servers must keep track
of streams separately in order to notify them when the server is
quiescing.

Modifications:

- Propagate the `ChannelShouldQuiesceEvent` to child channels

Result:

Child channels can watch for `ChannelShouldQuiesceEvent`s
@glbrntt glbrntt added the 🔨 semver/patch No public API change. label Sep 17, 2024
Copy link
Member

@FranzBusch FranzBusch left a comment

Choose a reason for hiding this comment

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

LGTM

@glbrntt glbrntt merged commit 6693a60 into apple:main Sep 18, 2024
6 of 7 checks passed
@glbrntt glbrntt deleted the propagate-should-quiesce branch September 18, 2024 06:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔨 semver/patch No public API change.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants