-
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
Jetty Websocket should have some API to handle timeouts #11358
Labels
Comments
lachlan-roberts
added a commit
that referenced
this issue
Oct 9, 2024
Signed-off-by: Lachlan Roberts <[email protected]>
lachlan-roberts
added a commit
that referenced
this issue
Oct 15, 2024
…outs Issue #11358 - Add API to handle timeouts in WebSocket
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jetty version(s)
12.0.x
Enhancement Description
Currently, when
WebSocketConnection.onIdleExpired
orWebSocketConnection.onReadTimeout
is called, the user of the API has no way to handle the timeout. CometD would be a prime user of this feature as it has its own timeout mechanism that currently clashes with the websocket one.We should add some API with which a user could plug a timeout handler, akin to what
request.addIdleTimeoutListener()
works for the Jetty Core API.The text was updated successfully, but these errors were encountered: