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

[BIND 10 Development]

#312: python msgq timeouts differ from c++ ones
-------------------------+--------------------------------------------------
      Reporter:  jelte   |        Owner:  stephen             
          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 => stephen


Comment:

 No you are right, I forgot about that one (perhaps because we are working
 on domainsockets here, but that may not be the case forever). I suspect
 this is what the original code had intended to do as well.

 Reintroduced class variables; code now does read-length followed by read-
 data, and keeps read data until it successfully read everything. If there
 is an EAGAIN in the meantime, it will keep the data. r2916

 Oh and the second case was a leftover from a bad test case, which i
 updated.

 Currently, on other errors, it will drop whatever has been read (while
 there may be a case where we get a timeout, i think it is more likely that
 the rest of the data will never come)

 Since you are gone this week, i'm reassigning this to Stephen.

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