BIND 10 #2690: use select instead of poll/kqueue in msgq

[BIND 10 Development]

#2690: use select instead of poll/kqueue in msgq
--------------------------------------+----------------------------------
                   Reporter:  jinmei  |                 Owner:
                       Type:  task    |                Status:  new
                   Priority:  medium  |             Milestone:  New Tasks
                  Component:  msgq    |              Keywords:
               CVSS Scoring:          |             Sensitive:  0
            Defect Severity:  N/A     |           Sub-Project:  Core
Feature Depending on Ticket:          |  Estimated Difficulty:  0
        Add Hours to Ticket:  0       |           Total Hours:  0
                  Internal?:  0       |
--------------------------------------+----------------------------------
 msgq uses kqueue when available and poll otherwise for handling
 network events.  We use kqueue because (the Python wrapper of) poll is
 known to have buggy behavior on some platforms, but it probably makes
 much more sense to unify the cases using select.  It should be most
 portable and is less likely to have surprising behavior.  msgq doesn't
 need to be highly scalable in terms of number of sockets, so select
 should be sufficient.  Unifying these cases will make the code simpler
 and easier to maintain.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2690>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development