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.

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

Issue #5044 - Refactor of Jetty WebSocket Upgrade Request/Response #5101

Conversation

lachlan-roberts
Copy link
Contributor

Issue #5044

The Jetty WebSocket API Interfaces UpgradeRequest, UpgradeResponse have been simplified with some server specific methods being moved to JettyServerUpgradeRequest and JettyServerUpgradeResponse which are now interfaces which extend the API interface.

This allowed me to remove all the empty and UnsupportedOperationException implementations in the various implementations.

Copy link
Contributor

@joakime joakime left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After a hangout review with @lachlan-roberts i'm good with this change as it stands.

+1 from me.

Signed-off-by: Lachlan Roberts <[email protected]>
@lachlan-roberts lachlan-roberts merged commit 1e7ce3a into jetty-10.0.x Aug 5, 2020
@lachlan-roberts lachlan-roberts deleted the jetty-10.0.x-5044-WebSocketUpgradeRequestResponse branch August 5, 2020 23:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Jetty WebSocket UpgradeRequest & UpgradeResponse types in Jetty 10
2 participants