The Bind message is send to the SCTP manager actor, which is obtained via StcpExt#manager in order to bind to a listening socket.
The Bind message is send to the SCTP manager actor, which is obtained via StcpExt#manager in order to bind to a listening socket. The manager replies either with a CommandFailed or the actor handling the listen socket replies with a Bound message. If the local port is set to 0 in the Bind message, then the Bound message should be inspected to find the actual port which was bound to.
The actor which will receive all incoming connection requests in the form of Connected messages.
The socket address to bind to; use port zero for automatic assignment (i.e. an ephemeral port, see Bound)
This specifies the number of unaccepted connections the O/S kernel will hold for this port before refusing connections.
Please refer to the SO object for a list of all supported options.
Adds the given address to the bound addresses for the channel's socket.
Adds the given address to the bound addresses for the channel's socket. The given address must not be the wildcard address. The channel must be first bound using bind before invoking this method, otherwise NotYetBoundException is thrown. Addresses subquently bound using this method are simply addresses as the SCTP port number remains the same for the lifetime of the channel. Adding addresses to a connected association is optional functionality. If the endpoint supports dynamic address reconfiguration then it may send the appropriate message to the peer to change the peers address lists.
The sender of a Bind command will—in case of success—receive confirmation in this form.
The sender of a Bind command will—in case of success—receive confirmation
in this form. If the bind address indicated a 0 port number, then the contained
localAddress
can be used to find out which port was automatically assigned.
Common interface for all commands which aim to close down an open connection.
This is the common trait for all commands understood by SCTP actors.
Whenever a command cannot be completed, the queried actor will reply with this message, wrapping the original command which failed.
The Connect message is sent to the SCTP manager actor, which is obtained via StcpExt#manager.
The Connect message is sent to the SCTP manager actor, which is obtained via StcpExt#manager. Either the manager replies with a CommandFailed or the actor handling the new connection replies with a Connected message.
is the address to connect to
optionally specifies a specific address to bind to
Please refer to the SO object for a list of all supported options.
The connection actor sends this message either to the sender of a Connect command (for outbound) or to the handler for incoming connections designated in the Bind message.
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 SCTP layer actors.
Each Send can optionally request a positive acknowledgment to be sent to the commanding actor.
Each Send can optionally request a positive acknowledgment to be sent to the commanding actor. If such notification is not desired the Send#ack must be set to an instance of this class. The token contained within can be used to recognize which write failed when receiving a CommandFailed message.
Whenever sctp message is read from a socket it will be transferred within this class to the handler actor which was designated in the Register message.
This message must be sent to a SCTP connection actor after receiving the Connected message.
This message must be sent to a SCTP connection actor after receiving the Connected message. The connection will not read any data from the socket until this message is received, because this message defines the actor which will receive all inbound data.
The actor which will receive all incoming data and which will be informed when the connection is closed.
Send data to the SCTP connection.
Send data to the SCTP connection. If no ack is needed use the special
NoAck
object. The connection actor will reply with a CommandFailed
message if the write could not be enqueued. If Send#wantsAck
returns true, the connection actor will reply with the supplied Send#ack
token once the write has been successfully enqueued to the O/S kernel.
Note that this does not in any way guarantee that the data will be
or have been sent! Unfortunately there is no way to determine whether
a particular write has been sent by the O/S.
Removes the given address from the bound addresses for the channel's socket.
Removes the given address from the bound addresses for the channel's socket. The given address must not be the wildcard address. The channel must be first bound using bind before invoking this method, otherwise NotYetBoundException is thrown. If this method is invoked on a channel that does not have address as one of its bound addresses or that has only one local address bound to it, then this method throws IllegalUnbindException. The initial address that the channel's socket is bound to using bind may be removed from the bound addresses for the channel's socket. Removing addresses from a connected association is optional functionality. If the endpoint supports dynamic address reconfiguration then it may send the appropriate message to the peer to change the peers address lists.
The sender of an Unbind command will receive confirmation through this message once the listening socket has been closed.
An abort operation will not flush pending writes and will issue a SCTP ABORT command to the O/S kernel which should result in a TCP_RST packet being sent to the peer.
An abort operation will not flush pending writes and will issue a SCTP ABORT command to the O/S kernel which should result in a TCP_RST packet being sent to the peer. The sender of this command and the registered handler for incoming data will both be notified once the socket is closed using a Aborted message.
The connection has been aborted in response to an Abort command.
A normal close operation will first flush pending writes and then close the socket.
A normal close operation will first flush pending writes and then close the socket. The sender of this command and the registered handler for incoming data will both be notified once the socket is closed using a Closed message.
The connection has been closed normally in response to a Close command.
The connection has been half-closed by us and then half-close by the peer in response to a ConfirmedClose command.
Default NoAck instance which is used when no acknowledgment information is explicitly provided.
Default NoAck instance which is used when no acknowledgment information is
explicitly provided. Its “token” is null
.
The peer has closed its writing half of the connection.
Sends a shutdown command to the remote peer, effectively preventing any new data from being written to the socket by either peer.
Sends a shutdown command to the remote peer, effectively preventing any new data from being written to the socket by either peer. The channel remains open to allow the for any data (and notifications) to be received that may have been sent by the peer before it received the shutdown command. The sender of this command and the registered handler for incoming data will both be notified once the socket is closed using a ConfirmedClosed message.
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 Bound message).
Java API: retrieve the Sctp extension for the given system.
Java API: retrieve the Sctp extension for the given system.