BIND 10 #1918: Msgq should connect to msgq

BIND 10 Development do-not-reply at isc.org
Sun Apr 29 09:40:13 UTC 2012


#1918: Msgq should connect to msgq
-------------------------------------+-------------------------------------
            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
-------------------------------------+-------------------------------------
 Currently, the msgq daemon only routes the messages. We want to be able to
 send
 and receive actual messages from the daemon as well. The easiest way is
 probably to use the usual libraries and connect to the socket ‒ the amount
 of
 messages send and received by the daemon itself will probably be small, so
 the
 overhead is not important.

 If we want to use the usual libraries, we may want to wait for #1917 to
 use the
 new version right away. This will not be much useful without the methods
 of
 #1915 yet anyway.

 For future commands and consistency, the connection should be full-blown
 ModuleCCSession with a spec file.

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


More information about the bind10-tickets mailing list