BIND 10 #1924: Msgq undeliverable notifications

[BIND 10 Development]

#1924: Msgq undeliverable notifications
-------------------------------------+-------------------------------------
            Reporter:  vorner        |                        Owner:
                Type:  task          |                       Status:  new
            Priority:  medium        |                    Milestone:  Next-
           Component:  msgq          |  Sprint-Proposed
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  6             |  Feature Depending on Ticket:  msgq-
         Total Hours:  0             |  ng
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by vorner):

 * milestone:   => Next-Sprint-Proposed


Comment:

 Putting to next-sprint-proposed as a base for proper handling of errors,
 not by
 timeouts. We probably should add an optional parameter to the `group_send`
 (or
 some other method) to allow specifying if the message needs an answer. The
 msgq
 should send the error as if from the recipient, so the following blocking
 receive picks it up.

 We probably don't want to do the extended addressing now, so don't
 consider
 #1923 as dependency.

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