BIND 10 #2975: Create initial DnsClient class

[BIND 10 Development]

#2975: Create initial DnsClient class
-------------------------------------+-------------------------------------
            Reporter:  tmark         |                        Owner:
                Type:  enhancement   |                       Status:  new
            Priority:  medium        |                    Milestone:
           Component:  dhcp          |  Sprint-DHCP-20130606
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  DHCP          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Description changed by tmark:

Old description:

> Define the public interface for !DnsClient class and create the initial
> stubimplementation.  The interface should support methods for:
> 1. Packet Construction, given the following data:
>     a: update type
>     b: zone
>     b: pre-requisites
>     c: updates
>
> Initial packet wire format will be JSON. The interface should be designed
> such that it readily supports alternative formats.
>
> 2. Packet exchange given:
>     a: constructed packet
>     b: server information
>     c: callback method
>
> Note that it would be best if the callback supported setting it to a
> class instance method, NOT a static function.

New description:

 Define the public interface for !DnsClient class and create the initial
 stubimplementation.  The interface should support methods for:
 1. Packet Construction, given the following data:
     a: update type
     b: zone
     b: pre-requisites
     c: updates

 Initial packet wire format will be JSON. The interface should be designed
 such that it readily supports alternative formats.

 2. Packet exchange given:
     a: constructed packet
     b: server information
     c: isc::asiolink io_service
     d: callback handler

 The class should accept an io_service either in its constructor or
 providing setter method.  This allows the invoking layer to control what
 io_service is used to monitor the packet IO. Note that it would be best if
 the callback supported setting it to a class instance method, NOT a static
 function.

--

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