-
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 UpgradeRequest & UpgradeResponse types in Jetty 10 #5044
Comments
lachlan-roberts
added a commit
that referenced
this issue
Jul 30, 2020
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
lachlan-roberts
added a commit
that referenced
this issue
Jul 30, 2020
… to ClientUpgradeRequest Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
lachlan-roberts
added a commit
that referenced
this issue
Jul 30, 2020
…uest Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
lachlan-roberts
added a commit
that referenced
this issue
Jul 30, 2020
… API interfaces Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
lachlan-roberts
added a commit
that referenced
this issue
Jul 30, 2020
…ty-websocket-server Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
lachlan-roberts
added a commit
that referenced
this issue
Aug 5, 2020
…adeRequestResponse Issue #5044 - Refactor of Jetty WebSocket Upgrade Request/Response
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jetty version
10.0.x
Description
The
UpgradeRequest
andUpgradeResponse
types in jetty 10 seem like they could use some simplification.There is the API
UpgradeRequest
andUpgradeResponse
. The Server APIJettyServerUpgradeRequest
andJettyServerUpgradeResponse
which do not extend the API interfaces. Then there are heaps of Adapters and Delegate classes for these to convert between different interfaces. And some of the methods on these remain unimplemented.The text was updated successfully, but these errors were encountered: