BIND 10 #2231: Allow sub-second timeouts in interface manager "receive" functions

[BIND 10 Development]

#2231: Allow sub-second timeouts in interface manager "receive" functions
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  stephen                            |                Status:  reviewing
                       Type:  task   |             Milestone:  Sprint-
                   Priority:         |  DHCP-20120917
  medium                             |            Resolution:
                  Component:  dhcp   |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DHCP
            Defect Severity:  N/A    |  Estimated Difficulty:  0
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by marcin):

 * owner:  marcin => UnAssigned
 * status:  accepted => reviewing


Comment:

 Added second parameter to receiveX functions: timestamp_usec representing
 microsecond precision timeout value and two unit tests that check if
 setting timeout really makes receiveX functions wait for specified amount
 of time (number of seconds + number of milliseconds).

 The receiveX functions expect that sub-second timeouts will be less than 1
 million (equals to 1s). This is an implication of the fact that function
 arguments are used to set timeval structure fields and tv.usec in timeval
 structure is expected to be less than 1 million
 (http://www.gnu.org/software/libc/manual/html_node/Elapsed-Time.html).
 Appropriate unit test for usec value has been added.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2231#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development