class EE::Network::SocketSelector¶
Overview¶
Multiplexer that allows to read from multiple sockets
Socket selectors provide a way to wait until some data is available on a set of sockets, instead of just one. More…
#include <socketselector.hpp> class SocketSelector { public: // construction SocketSelector(); SocketSelector(const SocketSelector& copy); ~SocketSelector(); // methods void add(Socket& socket); void remove(Socket& socket); void clear(); bool wait(Time timeout = Time::Zero); bool isReady(Socket& socket) const; SocketSelector& operator=(const SocketSelector& right); };
Detailed Documentation¶
Multiplexer that allows to read from multiple sockets
Socket selectors provide a way to wait until some data is available on a set of sockets, instead of just one. This is convenient when you have multiple sockets that may possibly receive data, but you don’t know which one will be ready first. In particular, it avoids to use a thread for each socket; with selectors, a single thread can handle all the sockets.
All types of sockets can be used in a selector:
EE::NetworkTcpListener
EE::NetworkTcpSocket
EE::NetworkUdpSocket
A selector doesn’t store its own copies of the sockets (socket classes are not copyable anyway), it simply keeps a reference to the original sockets that you pass to the “add” function. Therefore, you can’t use the selector as a socket container, you must store them oustide and make sure that they are alive as long as they are used in the selector.
Using a selector is simple:
populate the selector with all the sockets that you want to observe
make it wait until there is data available on any of the sockets
test each socket to find out which ones are ready
Usage example:
// Create a socket to listen to new connections TcpListener listener; listener.listen(55001); // Create a list to store the future clients std::vector<TcpSocket*> clients; // Create a selector SocketSelector selector; // Add the listener to the selector selector.add(listener); // Endless loop that waits for new connections while (running) { // Make the selector wait for data on any socket if (selector.wait()) { // Test the listener if (selector.isReady(listener)) { // The listener is ready: there is a pending connection TcpSocket* client = new TcpSocket; if (listener.accept(*client) == Socket::Done) { // Add the new client to the clients list clients.push_back(client); // Add the new client to the selector so that we will // be notified when he sends something selector.add(*client); } else { // Error, we won't get a new connection, delete the socket delete client; } } else { // The listener socket is not ready, test all other sockets (the clients) for (std::vector<TcpSocket*>::iterator it = clients.begin(); it != clients.end(); ++it) { TcpSocket& client = **it; if (selector.isReady(client)) { // The client has sent some data, we can receive it Packet packet; if (client.Receive(packet) == Socket::Done) { ... } } } } } }
See also:
Construction¶
SocketSelector()
Default constructor.
SocketSelector(const SocketSelector& copy)
Copy constructor.
Parameters:
copy |
Instance to copy |
~SocketSelector()
Destructor.
Methods¶
void add(Socket& socket)
Add a new socket to the selector This function keeps a weak reference to the socket, so you have to make sure that the socket is not destroyed while it is stored in the selector. This function does nothing if the socket is not valid.
Parameters:
socket |
Reference to the socket to add |
See also:
Remove, Clear
void remove(Socket& socket)
Remove a socket from the selector This function doesn’t destroy the socket, it simply removes the reference that the selector has to it.
Parameters:
socket |
Reference to the socket to remove |
See also:
Add, Clear
void clear()
Remove all the sockets stored in the selector This function doesn’t destroy any instance, it simply removes all the references that the selector has to external sockets.
See also:
Add, Remove
bool wait(Time timeout = Time::Zero)
Wait until one or more sockets are ready to receive This function returns as soon as at least one socket has some data available to be received. To know which sockets are ready, use the isReady function. If you use a timeout and no socket is ready before the timeout is over, the function returns false.
Parameters:
timeout |
Maximum time to wait, (use Time::Zero for infinity) |
Returns:
True if there are sockets ready, false otherwise
See also:
IsReady
bool isReady(Socket& socket) const
Test a socket to know if it is ready to receive data This function must be used after a call to Wait, to know which sockets are ready to receive data. If a socket is ready, a call to receive will never block because we know that there is data available to read. Note that if this function returns true for a TcpListener, this means that it is ready to accept a new connection.
Parameters:
socket |
Socket to test |
Returns:
True if the socket is ready to read, false otherwise
See also:
IsReady
SocketSelector& operator=(const SocketSelector& right)
Overload of assignment operator.
Parameters:
right |
Instance to assign |
Returns:
Reference to self