Allows to configure the poll(2) system call based mechanism.
It is also a widely available mechanism on POSIX envirionments, but not on Microsoft Windows. It doesn't have some limitations found on select(2) call, but it is known to not scale very well handling big socket sets as happens with select(2) (VORTEX_IO_WAIT_SELECT).
This mechanism solves the runtime limitation that provides select(2), making it possible to handle any number of connections without providing any previous knowledge during the compilation process.
Several third party tests shows it performs badly while handling many connections compared to (VORTEX_IO_WAIT_EPOLL) epoll(2).
However, reports showing that results, handles over 50.000 connections at the same time (up to 400.000!). In many cases this is not going your production environment.
At the same time, many reports (and our test results) shows that select(2), poll(2) and epoll(2) performs the same while handling up to 10.000 connections at the same time.