If this field is set with an IP address or domain name prior to initialisation, an attempt to connect to that location will be made when the NetSocket is initialised. Post-initialisation this field cannot be set by the client, however calls to Connect() will result in it being updated so that it always reflects the named address of the current connection.

Incoming connections to NetSocket objects are queued until they are answered by the object. Setting the Backlog adjusts the maximum number of connections on the queue, which otherwise defaults to 10.

If the backlog is exceeded, subsequent connections to the socket should expect a connection refused error.

This is a free-entry field value that can store client data for future reference.

The ClientLimit value limits the maximum number of IP addresses that can be connected to the socket at any one time. For socket limits per client, see the SocketLimit field.

This field describes the last error that occurred during a NetSocket operation:

In the case where a NetSocket object enters the NTC::DISCONNECTED state from the NTC::CONNECTED state, this field can be used to determine how a TCP connection was closed.

The client can define a function in this field to receive notifications whenever the state of the socket changes - typically connection messages.

In server mode, the function must follow the prototype Function(*NetSocket, *ClientSocket, NTC State). Otherwise Function(*NetSocket, NTC State).

The NetSocket parameter refers to the NetSocket object to which the function is subscribed. In server mode, ClientSocket refers to the ClientSocket on which the state has changed.

The Incoming field can be set with a custom function that will be called whenever the socket receives data. The function prototype for C++ is ERR Incoming(*NetSocket, APTR Meta). For Fluid use function Incoming(NetSocket).

The NetSocket parameter refers to the NetSocket object. Meta is optional userdata from the FUNCTION.

Retrieve data from the socket with the Read() action. Reading at least some of the data from the socket is compulsory - if the function does not do this then the data will be cleared from the socket when the function returns. If the callback function returns/raises ERR::Terminate then the Incoming field will be cleared and the function will no longer be called. All other error codes are ignored.

This field limits the size of incoming and outgoing message queues (each socket connection receives two queues assigned to both incoming and outgoing messages). The size is defined in bytes. Sending or receiving messages that overflow the queue results in the connection being terminated with an error.

The default setting is 1 megabyte.

The Outgoing field can be set with a custom function that will be called whenever the socket is ready to send data. The function must be in the format ERR Outgoing(*NetSocket, OBJECTPTR Context)

The NetSocket parameter refers to the NetSocket object. The Context refers to the object that set the Outgoing field.

To send data to the NetSocket object, call the Write() action. If the callback function returns ERR::Terminate then the Outgoing field will be cleared and the function will no longer be called. All other error codes are ignored.

The Outgoing field is ineffective if the NetSocket is in server mode (target a connected client socket instead).

The State reflects the connection state of the NetSocket. If the Feedback field is defined with a function, it will be called automatically whenever the state is changed. Note that the ClientSocket parameter will be NULL when the Feedback function is called.

Note that in server mode this State value should not be used as it cannot reflect the state of all connected client sockets. Each ClientSocket carries its own independent State value for use instead.

In server mode, the NetSocket will maintain a count of the total number of clients currently connected to the socket. You can read the total number of connections from this field.

In client mode, this field is always set to zero.

After an encrypted connection has been made to a server, the ValidCert field can be used to determine the validity of the server's certificate.

If encrypted communication is not supported, ERR::NoSupport is returned. If the certificate is valid or the connection is not encrypted, a value of zero is returned to indicate that the connection is valid.