BIND 10 #2111: Define a dedicated result context and additional record handling.

[BIND 10 Development]

#2111: Define a dedicated result context and additional record handling.
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  jinmei                             |                Status:  new
                       Type:  task   |             Milestone:  Next-Sprint-
                   Priority:         |  Proposed
  medium                             |            Resolution:
                  Component:  data   |             Sensitive:  0
  source                             |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
  scalable inmemory                  |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Description changed by jinmei:

Old description:

> This is a revised version of current `RBNodeResultContext`
> and `InMemoryZoneFinder::Context`.  But right now additional shortcut
> is not available, so it's actually pretty simple.
>
> Iterate over each RDATA of the given RRset using the encoded version
> of iterator, and use findNode() to get the node for each name field of
> the RDATA whose attribute indicates additional handling is needed.
> Then go through the nodes' `RdataSet` to find specified type of data.
> Construct `TreeNodeRRset` for them and push them to the result.
>
> One open question is whether we should distinguish "glue ok" case or
> not.  I'm now inclined to skip this differentiation, but we can
> discuss it.

New description:

 This is a revised version of current `RBNodeResultContext`
 and `InMemoryZoneFinder::Context`.  But right now additional shortcut
 is not available, so it's actually pretty simple.

 Iterate over each RDATA of the given RRset using the encoded version
 of iterator, and use findNode() to get the node for each name field of
 the RDATA whose attribute indicates additional handling is needed.
 Then go through the nodes' `RdataSet` to find specified type of data.
 Construct `TreeNodeRRset` for them and push them to the result.

 One open question is whether we should distinguish "glue ok" case or
 not.  I'm now inclined to skip this differentiation, but we can
 discuss it.

 Depend on #2096, and in practice, on #2107, #2108 and #2109 (and
 even #2110 for comprehensive support).

--

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