-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Explicit demand control in WebSocket endpoints with only onWebSocketFrame() #11307
Labels
Bug
For general bugs on Jetty side
Comments
See #11304. |
lachlan-roberts
added a commit
that referenced
this issue
Oct 3, 2024
…ly onWebSocketFrame Signed-off-by: Lachlan Roberts <[email protected]>
lachlan-roberts
added a commit
that referenced
this issue
Nov 15, 2024
…meHandler-demand Issue #11307 - Explicit demand control in WebSocket endpoints with only onWebSocketFrame
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jetty version(s)
12+
Description
If a WebSocket endpoint only overrides
onWebSocketFrame()
it currently has no explicit control over the demand, because the implementation expects other methods to be present, and the other methods to control the demand explicitly.There should be a way to explicitly control the demand if an application want to deal only with frames.
The text was updated successfully, but these errors were encountered: