-
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
WebSocketClient constructor cleanup (and deprecations) #3730
Labels
Comments
This was referenced Jun 4, 2019
joakime
added a commit
that referenced
this issue
Dec 13, 2019
+ Introducing HttpContainerScope to track HttpClient specific ByteBufferPool, SslContextFactory, and Executor. + New private WebSocketClient constructor that use HttpContainerScope + Deprecated many constructors as irrelevant now that HttpClient is an option to create a WebSocketClient. Signed-off-by: Joakim Erdfelt <[email protected]>
Opened PR #4423 |
joakime
added a commit
that referenced
this issue
Dec 18, 2019
Signed-off-by: Joakim Erdfelt <[email protected]>
joakime
added a commit
that referenced
this issue
Dec 18, 2019
Signed-off-by: Joakim Erdfelt <[email protected]>
joakime
added a commit
that referenced
this issue
Dec 18, 2019
Signed-off-by: Joakim Erdfelt <[email protected]>
joakime
added a commit
that referenced
this issue
Dec 19, 2019
Signed-off-by: Joakim Erdfelt <[email protected]>
joakime
added a commit
that referenced
this issue
Dec 19, 2019
Signed-off-by: Joakim Erdfelt <[email protected]>
joakime
added a commit
that referenced
this issue
Dec 19, 2019
Signed-off-by: Joakim Erdfelt <[email protected]>
joakime
added a commit
that referenced
this issue
Dec 19, 2019
…e-cleanup Issue #3730 - Cleaning up Scopes in WebSocketClient
joakime
changed the title
Cleanup WebSocket Scopes / Configuration confusion
WebSocketClient constructor cleanup (and deprecations)
Dec 20, 2019
This was referenced Dec 16, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While performing a review of PR #3651 it has become apparent that the websocket scopes and configuration behaviors in Jetty 9.4.x is confusing.
Should clean this up to be less confusing and better documented.
The text was updated successfully, but these errors were encountered: