BIND 10 #2091: use encoded name data in RBNode

[BIND 10 Development]

#2091: use encoded name data in RBNode
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  vorner
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20120731
  medium                             |            Resolution:
                  Component:  data   |             Sensitive:  0
  source                             |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  5
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
  scalable inmemory                  |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:11 vorner]:

 > > Replying to [comment:7 vorner]:
 > > Not tested, but you're probably right, and that's not a longer term
 > > intention.  I clarified that as comments in ~ZoneData().
 >
 > Well, you clarified the longer-term intention, but not the current
 restriction to use a new segment for each zone. I think that should be
 mentioned in the doxygen.

 Hmm, I have no problem with that, but I'm not sure where in doxygen
 (for public interface) we describe it...right now the use of memory
 segments for zone data is completely local to the implementation.  So,
 in terms of the API the user doesn't even aware that a notion of
 "memory segment" is used inside, much less whether they can share a
 single segment for multiple zones.

 This will change later of this entire scalability feature.  At this
 point we'll probably use a single segment for a set or all of zones,
 or if for some reason we still need to use separate ones for separate
 zones we can describe it in doxygen for that part of API.

 If you want to explain it somewhere in doxygen right now and if you
 have a specific idea of where we do this, I'm okay with noting it
 there though.

 (I made a few minor changes to the current text and pushed it via the
 trac2091a branch).

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