BIND 10 #2538: Explain the format and purpose of ZoneTableSegment::create config parameter

[BIND 10 Development]

#2538: Explain the format and purpose of ZoneTableSegment::create config parameter
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  vorner                             |                Status:  new
                       Type:  task   |             Milestone:  New Tasks
                   Priority:         |              Keywords:
  medium                             |             Sensitive:  0
                  Component:  data   |           Sub-Project:  DNS
  source                             |  Estimated Difficulty:  0
               CVSS Scoring:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 The `ZoneTableSegment::create` takes a config parameter. It is currently
 ignored and it is not explained:
  * How it'll look like, what information it'll contain, etc.
  * Where it comes from. I don't think it is practical to ask users to
 write a
    config about the used segments for each zone, or something. IMO it
 should
    work just by turning the b10-memorymgr on in boss, and everything else
    should be auto-negotiated with it, or something. Things like if the
 data is
    passed to the auth (or other consumers) by a memory-mapped file, or
 shared
    memory, should be in the memorymgr configuration.

 Currently, everything that needs a zone table segment, just passes
 something like NullElement or some other dummy value. It's not clear where
 such config will appear at the place where the create is called.

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