BIND 10 #3008: Develop NameChange{Sender,Listener} classes.

[BIND 10 Development]

#3008: Develop NameChange{Sender,Listener} classes.
-------------------------------------+-------------------------------------
            Reporter:  tmark         |                        Owner:  tmark
                Type:  enhancement   |                       Status:
            Priority:  medium        |  assigned
           Component:  dhcp-ddns     |                    Milestone:
            Keywords:                |  Sprint-DHCP-20130703
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DHCP          |                 CVSS Scoring:
Estimated Difficulty:  0             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by tmark):

 * owner:   => tmark
 * status:  new => assigned


Old description:

> 2.2 Develop !NameChange{Sender,Listener} classes.
> Develop the classes for sending and receiving !NameChangeReqeusts.
>
> This will should structured as a client/server UDP socket based IPC.  It
> would be a good idea to abstract the solution in such a the actual IPC
> mechanism can be swapped,  socket vs db table etc.
>
> There is an open issue with how to "queue" requests from clients when the
> server (consumer) is not active.   For example, what do DHCP servers do
> with DNS update requests if D2 is not alive?
>
> An initial implementation may just throw them on floor.
>

> Listener class should support a instance method callback.  Our asiolink
> library seems to only support functions as callbacks.  It would be far
> more flexible if D2 IO supports class instance methods as callbacks.

New description:

 2.2 Develop !NameChange{Sender,Listener} classes.
 Develop the classes for sending and receiving !NameChangeReqeusts.

 This will should be structured as a client/server UDP socket based IPC.
 It would be a good idea to abstract the solution in such a way that the
 actual mechanism can be swapped,  socket vs db table etc.

 There is an open issue with how to "queue" requests from clients when the
 server (consumer) is not active.   For example, what do DHCP servers do
 with DNS update requests if D2 is not alive?

 An initial implementation may just throw them on floor.


 Listener class should support a instance method callback.  Our asiolink
 library seems to only support functions as callbacks.  It would be far
 more flexible if D2 IO supports class instance methods as callbacks.

--

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