BIND 10 #2283: [meta] avoid using getName() and getRdataIterator() for in-memory

[BIND 10 Development]

#2283: [meta] avoid using getName() and getRdataIterator() for in-memory
----------------------------------------+-----------------------------
                   Reporter:  jinmei    |                 Owner:
                       Type:  task      |                Status:  new
                   Priority:  medium    |             Milestone:
                  Component:  b10-auth  |            Resolution:
                   Keywords:            |             Sensitive:  0
            Defect Severity:  N/A       |           Sub-Project:  DNS
Feature Depending on Ticket:            |  Estimated Difficulty:  meta
        Add Hours to Ticket:  0         |           Total Hours:  0
                  Internal?:  0         |
----------------------------------------+-----------------------------
Description changed by jinmei:

Old description:

> In the new version of in-memory data source `RRset::getName()` and
> `RRset::getRdataIterator()` are more expensive than the generic
> versions.  So we'll need to allow specialization for the in-memory
> data source where we can skip these expensive methods in the query
> processing.
>
> The basic idea is to extend the finder context class so it will have
> specific methods for these cases, and implement optimized in-memory
> version.
>
> We can do this incrementally.
>
> The specific tickets are:
> - (This won't work) ~~#2060 ZoneFinder::Context::getAtOrigin, #2284 for
> in-memory~~
> - #2309 define ZoneFinder::findAtOrigin(), #2310 for in-memory
> - #2058 ZoneFinder::Context::getDelegationProof, #2286 for in-memory
> - #2056 ZoneFinder::Context::getNegativeProof, #2285 for in-memory
> - #2057 ZoneFinder::Context::getWildcardProof, #2288 for in-memory
> - #2059 ZoneFinder::Context::getSynthesizedCNAME, #2287 for in-memory

New description:

 In the new version of in-memory data source `RRset::getName()` and
 `RRset::getRdataIterator()` are more expensive than the generic
 versions.  So we'll need to allow specialization for the in-memory
 data source where we can skip these expensive methods in the query
 processing.

 The basic idea is to extend the finder context class so it will have
 specific methods for these cases, and implement optimized in-memory
 version.

 We can do this incrementally.

 The specific tickets are:
 - (This won't work) ~~#2060 ZoneFinder::Context::getAtOrigin, #2284 for
 in-memory~~
 - #2309 define ZoneFinder::findAtOrigin(), #2310 for in-memory
 - #2058 ZoneFinder::Context::getDelegationProof, #2286 for in-memory
 - #2056 ZoneFinder::Context::getNegativeProof, #2336 and #2337 for in-
 memory
 - #2057 ZoneFinder::Context::getWildcardProof, #2288 for in-memory
 - #2059 ZoneFinder::Context::getSynthesizedCNAME, #2287 for in-memory

--

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