96feca1d23
Motivation: SslHandler must generate control data as part of the TLS protocol, for example to do handshakes. SslHandler doesn't capture the status of the future corresponding to the writes when writing this control (aka non-application data). If there is another handler before the SslHandler that wants to fail these writes the SslHandler will not detect the failure and we must wait until the handshake timeout to detect a failure. Modifications: - SslHandler should detect if non application writes fail, tear down the channel, and clean up any pending state. Result: SslHandler detects non application write failures and cleans up immediately. |
||
---|---|---|
.. | ||
src | ||
pom.xml |