-
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
websocket suspend when input closed #3734
Comments
I think ISE is probably the most correct API choice... but if there is need we could maintain behaviour with jetty-9 as no-op is OKish. @joakime your thoughts? |
I personally like the ISE. |
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
changed suspend while closed to throw ISE in both jetty-9.4.x and jetty-10.0.x |
suspending a WebSocket when it is already input closed has different behavior from jetty-9 to jetty-10
SuspendResumeTest.testSuspendAfterClose()
has been disabled in jetty-10 as I was not sure which approach was correct.The text was updated successfully, but these errors were encountered: