[ ... ]
>> When a select returns that a fd is ready, remove the fd from the set and
>> throw an event into the queue that states, for instance, fd "x" is ready
>> for reading, and go back to selecting again.  Then have a pool of threads
>> reading from the queue and processing requests.  After the threads read or
>> write to the appropriate fd, re-add the fd to the set using a mutex or
>> something, and then signal the thread that is selecting to reload its set
>> and select again (this is somewhat of a simplification but you get the
>> idea).

>> This way you only need one thread selecting, but all threads can operate
>> on the results of it.

>    Imagine you're handling 1,000 connections and you find work to do on
>100 of them. You will wind up restarting the 'select' 100-ish times as
>you add each one back to the set. In most cases, you're better off
>reading all the data before restarting 'select'. (Not necessarily
>processing it, just reading it.)