BIND 10 #1015: unify configuration/command code for auth and resolver

[BIND 10 Development]

#1015: unify configuration/command code for auth and resolver
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  task          |                       Status:  new
            Priority:  major         |                    Milestone:  Next-
           Component:  resolver      |  Sprint-Proposed
           Sensitive:  0             |                     Keywords:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 Looking at the (b10) resolver configuration code, I start feeling
 we should unify the server configuration code for both b10-auth and
 b10-resolver (and, probably the DHCP servers eventually).

 The current implementation for b10-resolver is a big single method
 that is responsible for everything: parsing config parameters,
 building internal configuration data from the passed param, and doing
 this for all parameters in the single function.  Clearly this approach
 won't scale as we add more parameters.

 My suggestion is to use the auth/auth_config.{h,cc} and
 auth/command.{h,cc} by moving them to lib/server_common (and rename
 them appropriately), adjusting them if necessary so that they can work
 with the resolver, and have the resolver use it.

 We should perhaps also consider making the hardcoded factory logic
 in auth_config.cc:createAuthConfigParser() more generic using this
 opportunity.

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