BIND 10 #1928: Msgq tests: failure modes

[BIND 10 Development]

#1928: Msgq tests: failure modes
-------------------------------------+-------------------------------------
            Reporter:  vorner        |                        Owner:
                Type:  task          |                       Status:  new
            Priority:  medium        |                    Milestone:  Next-
           Component:  msgq          |  Sprint-Proposed
           Sensitive:  0             |                     Keywords:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:  msgq-
         Total Hours:  0             |  ng
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 In addition to #1927 (which should be done first, as we may want to reuse
 a lot
 of the code there), we should also test the failure modes, like unclean
 connection drops (in the middle of receiving or sending a message),
 protocol
 violations, infinite blocking, sending a message to self, etc. We need to
 make
 sure the daemon will not crash and will continue to provide service to at
 least
 other connections.

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