Scala API: attach the two given stages such that the command output of the first is fed into the command input of the second, and the event output of the second is fed into the event input of the first.
Scala API: attach the two given stages such that the command output of the first is fed into the command input of the second, and the event output of the second is fed into the event input of the first. In other words: sequence the stages such that the left one is on top of the right one.
the right or lower pipeline stage
a pipeline stage representing the sequence of the two stages
Implement this method to generate this stage’s pair of command and event functions.
Implement this method to generate this stage’s pair of command and event functions.
INTERNAL API: do not use this method to instantiate a pipeline!
Scala API: combine the two stages such that the command pipeline of the left stage is used and the event pipeline of the right, discarding the other two sub-pipelines.
Scala API: combine the two stages such that the command pipeline of the left stage is used and the event pipeline of the right, discarding the other two sub-pipelines.
the event pipeline
a pipeline stage using the left command pipeline and the right event pipeline
(sslTlsSupport: StringAdd).self
(sslTlsSupport: StringFormat).self
(sslTlsSupport: ArrowAssoc[SslTlsSupport]).x
(Since version 2.10.0) Use leftOfArrow
instead
(sslTlsSupport: Ensuring[SslTlsSupport]).x
(Since version 2.10.0) Use resultOfEnsuring
instead
This pipeline stage implements SSL / TLS support, using an externally configured javax.net.ssl.SSLEngine. It operates on the level of Tcp.Event and Tcp.Command messages, which means that it will typically be one of the lowest stages in a protocol stack. Since SSLEngine relies on contiguous transmission of a data stream you will need to handle backpressure from the TCP connection actor, for example by using a BackpressureBuffer underneath the SSL stage.
Each instance of this stage has a scratch ByteBuffer of approx. 18kiB allocated which is used by the SSLEngine.
One thing to keep in mind is that there's no support for half-closed connections in SSL (but SSL on the other side requires half-closed connections from its transport layer).
This means: 1. keepOpenOnPeerClosed is not supported on top of SSL (once you receive PeerClosed the connection is closed, further CloseCommands are ignored) 2. keepOpenOnPeerClosed should always be enabled on the transport layer beneath SSL so that one can wait for the other side's SSL level close_notify message without barfing RST to the peer because this socket is already gone