BIND 10 #2170: Consistent place to configure socket file paths

[BIND 10 Development]

#2170: Consistent place to configure socket file paths
-------------------------------------+-------------------------------------
            Reporter:  shane         |                        Owner:
                Type:  task          |                       Status:  new
            Priority:  medium        |                    Milestone:  New
           Component:  Unclassified  |  Tasks
           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
-------------------------------------+-------------------------------------
 This came up during a recent BIND 10 team call:

 WeeklyMinutes20120712#Consistentwaytodefinepathstosocketfilesforalluses

 There are several places where this type of information is stored:
 - src/lib/python/bind10_config.py
 - in specific python scripts like xfrout.py
 - in some C++ files like auth/common.{h,cc}

 Jinmei reports:

 {{{
 It's just a mess.  When you need to know the path, you'll need to
 find multiple places.  When you need to add a new path, there can be
 several ways and it's also possible that you invent yet another
 place.  Also, there are some inconsistent cases like #1903.

 So, what exactly I would envision is:

 - introduce a unified place to define this information for all
   modules.  ideally this should be the only source for both Python and
   C++.
 - Python scripts and C++ sources refer to this place and use the
   information appropriately.
 - Document the policy and how you add new things to the unified place.
 }}}

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