RawSecureSocket provides a secure (SSL or TLS) network connection. Client connections to a server are provided by calling RawSecureSocket.connect. A secure server, created with RawSecureServerSocket, also returns RawSecureSocket objects representing the server end of a secure connection. The certificate provided by the server is checked using the trusted certificates set in the SecurityContext object. The default SecurityContext object contains a built-in set of trusted root certificates for well-known certificate authorities.
true
.
true
.
This is a one-shot listener, and writeEventsEnabled must be set
to true again to receive another write event.
test
accepts any element provided by this stream. [...]
Stream<R>
. [...]
needle
occurs in the elements provided by this stream. [...]
index
th data event of this stream. [...]
test
accepts all elements provided by this stream. [...]
test
. [...]
combine
. [...]
action
on each element of this stream. [...]
test
. [...]
streamConsumer
. [...]
len
bytes from the socket. This function is
non-blocking and will only return data if data is available. The
number of bytes read can be less then len
if fewer bytes are
available for immediate reading. If no data is available null
is returned.
combine
. [...]
direction
. Calling shutdown will never
throw an exception and calling it several times is supported. Calling
shutdown with either SocketDirection.both or SocketDirection.receive
can result in a RawSocketEvent.readClosed event.
test
. [...]
count
data events from this stream. [...]
test
. [...]
count
data events of this stream. [...]
test
is successful. [...]
streamTransformer
to this stream. [...]
count
bytes of the buffer from offset
buffer offset to
the socket. The number of successfully written bytes is returned. This
function is non-blocking and will only write data if buffer space is
available in the socket. [...]
socket
and starts client side TLS
handshake to make the communication secure. When the returned
future completes the RawSecureSocket has completed the TLS
handshake. Using this function requires that the other end of the
connection is prepared for TLS handshake. [...]
socket
and starts server side TLS
handshake to make the communication secure. When the returned
future completes the RawSecureSocket has completed the TLS
handshake. Using this function requires that the other end of the
connection is going to start the TLS handshake. [...]