Affects: Latest
Expected Behavior
WebSocketClient should give an ability to configure timeout fro the handshake operation, and not discards established Web-Socket connection. for the reactor netty solution was described in this comment
Actual Behavior
Reactor timeout applied after execute acts as a response timeout for the Http request, but as well discards established Web-Socket connection.
In the Reactor-netty there are 2 separate methods for establishing Handshake and maintaining the established connections in WebsocketFinalizer and it will be handy to have similar API in WebSocketClient.
Comment From: rstoyanchev
I don't understand the request to not discard the WebSocket connection since the handshake needs to succeed before there is a WebSocket connection. Could you clarify that and provide some examples of how you would like the API to change, of how the use of Reactor Netty would change in ReactorNettyWebSocketClient
?
Comment From: spring-projects-issues
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
Comment From: spring-projects-issues
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.