The Bind message is send to the TCP manager actor, which is obtained via akka.io.Tcp.TcpExt#manager in order to bind to a listening socket.
The sender of a akka.io.Tcp.Bind command will—in case of success—receive confirmation in this form.
Common interface for all commands which aim to close down an open connection.
This is the common trait for all commands understood by TCP actors.
Whenever a command cannot be completed, the queried actor will reply with this message, wrapping the original command which failed.
A write command which aggregates two other write commands.
The Connect message is sent to the TCP manager actor, which is obtained via akka.io.Tcp.TcpExt#manager.
This is the common interface for all events which indicate that a connection has been closed or half-closed.
The connection has been closed due to an IO error.
Common interface for all events generated by the TCP layer actors.
The common interface for akka.io.Command and akka.io.Tcp.Event.
Each akka.io.Tcp.WriteCommand can optionally request a positive acknowledgment to be sent to the commanding actor.
Whenever data are read from a socket they will be transferred within this class to the handler actor which was designated in the akka.io.Tcp.Register message.
This message must be sent to a TCP connection actor after receiving the akka.io.Tcp.Connected message.
The sender of an akka.io.Tcp.Unbind command will receive confirmation through this message once the listening socket has been closed.
Write data to the TCP connection.
count bytes starting at
position from file at
filePath to the connection.
useResumeWriting is in effect as indicated in the akka.io.Tcp.Register message,
the akka.io.Tcp.ResumeWriting command will be acknowledged by this message type, upon
which it is safe to send at least one write.
An abort operation will not flush pending writes and will issue a TCP ABORT command to the O/S kernel which should result in a TCP_RST packet being sent to the peer.
The connection has been aborted in response to an akka.io.Tcp.Abort command.
A normal close operation will first flush pending writes and then close the socket.
The connection has been closed normally in response to a akka.io.Tcp.Close command.
A confirmed close operation will flush pending writes and half-close the connection, waiting for the peer to close the other half.
The connection has been half-closed by us and then half-close by the peer in response to a akka.io.Tcp.ConfirmedClose command.
Default akka.io.Tcp.NoAck instance which is used when no acknowledgment information is explicitly provided.
The peer has closed its writing half of the connection.
This command needs to be sent to the connection actor after a akka.io.Tcp.SuspendReading command in order to resume reading from the socket.
useResumeWriting is in effect as was indicated in the akka.io.Tcp.Register message
then this command needs to be sent to the connection actor in order to re-enable
writing after a akka.io.Tcp.CommandFailed event.
Scala API: this object contains all applicable socket options for TCP.
Sending this command to the connection actor will disable reading from the TCP socket.
In order to close down a listening socket, send this message to that socket’s actor (that is the actor which previously had sent the akka.io.Tcp.Bound message).
Java API: retrieve Tcp extension for the given system.