BIND 10 #312: python msgq timeouts differ from c++ ones

[BIND 10 Development]

#312: python msgq timeouts differ from c++ ones
-------------------------+--------------------------------------------------
      Reporter:  jelte   |        Owner:  UnAssigned          
          Type:  defect  |       Status:  reviewing           
      Priority:  major   |    Milestone:  y2 6 month milestone
     Component:  msgq    |   Resolution:                      
      Keywords:          |    Sensitive:  0                   
Estimatedhours:  0.0     |        Hours:  0                   
      Billable:  1       |   Totalhours:  0                   
      Internal:  0       |  
-------------------------+--------------------------------------------------
Changes (by jelte):

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


Comment:

 I think this is ready for review; branches/trac312

 recvmsg(False) now raises an isc.cc.SessionTimeout error when no data is
 read after the default timeout expires, instead of returning (None, None).

 Modules and other libraries that call this are updated to correctly handle
 this change. cfgmgr.py play around a bit since it has one call that is
 supposed to block forever until data is read (before that call it sets the
 timeout to 0 and sets it back to the default if that call has returned)

 There is one TODO, about logging. Since adding logging would be the
 subject of another ticket, I left this TODO in so we are reminded to add a
 log message at that location.

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