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

BIND 10 Development do-not-reply at isc.org
Sat Sep 22 06:45:21 UTC 2012


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

 * milestone:  New Tasks => Next-Sprint-Proposed


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:
> - #2060 ZoneFinder::Context::getAtOrigin
> - #2058 ZoneFinder::Context::getDelegationProof
> - #2056 ZoneFinder::Context::getNegativeProof
> - #2057 ZoneFinder::Context::getWildcardProof
> - #2059 ZoneFinder::Context::getSynthesizedCNAME

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:
 - #2060 ZoneFinder::Context::getAtOrigin, #2284 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

--

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


More information about the bind10-tickets mailing list