BIND 10 #1985: eliminate duplicate hardcoding for ddns UNIX socket file both in auth and ddns (was: b10-auth should get ddns UNIX socket file from ddns config)

[BIND 10 Development]

#1985: eliminate duplicate hardcoding for ddns UNIX socket file both in auth and
ddns
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  jinmei                             |                Status:  new
                       Type:         |             Milestone:  Next-Sprint-
  defect                             |  Proposed
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  DNS
  b10-auth                           |  Estimated Difficulty:  0
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Description changed by jinmei:

Old description:

> On top of #1984, b10-auth should get the UNIX socket file path
> from the ddns configuration.  We'll then be able to deprecate
> getDDNSSocketPath() introduced in #1539.

New description:

 (Updating the ticket based on some followup discussion).

 Right now both b10-auth and b10-ddns hardcode the constant for the
 UNIX domain socket between them.  We should unify it some way based on
 the principle of "don't repeat yourself".

 Specifying it in the b10-ddns configuration was one idea to solve this
 issue, but that idea seemed to be controversial.  Other possible
 approaches are
 - have b10-ddns tells b10-auth its existence with additional
   information including the file path.  #1986 will also be resolved
   this way.
 - introduce some C++ header file for commonly used constants like
   this, also introduce a python wrapper that defines corresponding
   python constants, and have ddns and auth refer to these.

 Now this task would be requiring some design level considerations, and
 any prior estimations would be unreliable.  Maybe this should be a
 topic of the 1-week hardening sprint later.

--

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