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.

Sign up for GitHub

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

Jump to bottom

Create a way to close WebSocket flushers without always creating exception. #8137

Closed
lachlan-roberts opened this issue Jun 8, 2022 · 1 comment
Closed

Create a way to close WebSocket flushers without always creating exception. #8137

lachlan-roberts opened this issue Jun 8, 2022 · 1 comment
Assignees
@lachlan-roberts
Labels
Enhancement

Comments

@lachlan-roberts
Copy link
Contributor

Jetty version(s)
10+

Flushers in websocket need a way to be closed without creating an exception.
FragmentingFlusher
TransformingFlusher
DemandingFlusher
etc...

close could potentially be used, this would need to fail any existing entries, not allow new entries to be added and creating exception only if needed.
@lachlan-roberts lachlan-roberts self-assigned this Jun 8, 2022
@lachlan-roberts lachlan-roberts mentioned this issue Jun 8, 2022
Merged
@lachlan-roberts
Copy link
Contributor Author

fixed with #8155

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lachlan-roberts lachlan-roberts

Labels
Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lachlan-roberts