Default constructor
Destructor
Connect the socket to a remote peer.
Disconnect the socket from its remote peer.
Get the port to which the socket is bound locally.
Get the address of the connected peer.
Get the port of the connected peer to which the socket is connected.
Tell whether the socket is in blocking or non-blocking mode.
In blocking mode, this function will wait until the whole packet has been received. This function will fail if the socket is not connected.
Receive raw data from the remote peer.
Send raw data to the remote peer.
Send a formatted packet of data to the remote peer.
Set the blocking state of the socket.
Specialized socket using the TCP protocol.
TCP is a connected protocol, which means that a TCP socket can only communicate with the host it is connected to.
It can't send or receive anything if it is not connected.
The TCP protocol is reliable but adds a slight overhead. It ensures that your data will always be received in order and without errors (no data corrupted, lost or duplicated).
When a socket is connected to a remote host, you can retrieve informations about this host with the getRemoteAddress and getRemotePort functions. You can also get the local port to which the socket is bound (which is automatically chosen when the socket is connected), with the getLocalPort function.
Sending and receiving data can use either the low-level or the high-level functions. The low-level functions process a raw sequence of bytes, and cannot ensure that one call to Send will exactly match one call to Receive at the other end of the socket.
The high-level interface uses packets (see sf::Packet), which are easier to use and provide more safety regarding the data that is exchanged. You can look at the sf::Packet class to get more details about how they work.
The socket is automatically disconnected when it is destroyed, but if you want to explicitely close the connection while the socket instance is still alive, you can call disconnect.