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

Deprecate JettyWebSocketClient in favor of StandardWebSocketClient #29576

Closed
jhoeller opened this issue Nov 25, 2022 · 0 comments
Closed

Deprecate JettyWebSocketClient in favor of StandardWebSocketClient #29576

jhoeller opened this issue Nov 25, 2022 · 0 comments
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Milestone

Comments

@jhoeller
Copy link
Contributor

Related to #29575, we need to phase out JettyWebSocketClient since it is tied to Jetty 11 and not worth upgrading to the relocated client API in Jetty 12, effectively superseded by the Jakarta WebSocket based StandardWebSocketClient for our purposes. Let's therefore deprecate our two JettyWebSocketClient variants in 6.0.3 already, preparing for removal in 6.1.

@jhoeller jhoeller added in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement labels Nov 25, 2022
@jhoeller jhoeller added this to the 6.0.3 milestone Nov 25, 2022
@jhoeller jhoeller self-assigned this Nov 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

1 participant