-
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
Cannot customize Executor on WebSocketClient #10547
Comments
… HttpClient Signed-off-by: Joakim Erdfelt <[email protected]>
Signed-off-by: Joakim Erdfelt <[email protected]>
… HttpClient (#10548) * Issue #10547 - Allow Executor of WebSocketClient to be customized via HttpClient Signed-off-by: Joakim Erdfelt <[email protected]>
The fix for this issue in #10548 is not optimal, because we are now exposing explicitly 2 ways of passing executors, which is more confusing than before. We should hide the fact that |
The HttpClient and WebSocketComponents will now try to share as many components as possible. Signed-off-by: Simone Bordet <[email protected]>
Added tests after review. Signed-off-by: Simone Bordet <[email protected]>
The HttpClient and WebSocketComponents will now try to share as many components as possible. Signed-off-by: Simone Bordet <[email protected]>
Jetty version(s)
10.0.16
Jetty Environment
n/a
Java version/vendor
(use: java -version)
All
OS type/version
All
Description
If a developer wants to customize the Executor of the WebSocketClient, it is not possible, as the internal final WebSocketComponents is initialized with a new Executor from scratch, not using the one from the HttpClient (or other common / shared locations)
The text was updated successfully, but these errors were encountered: