BIND 10 #2109: redefine in-memory zone finder (basic)

[BIND 10 Development]

#2109: redefine in-memory zone finder (basic)
-------------------------------------+-------------------------------------
                   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:

> With #2108, the `InMemoryZoneFinder` can now concentrate on its
> find()-related tasks.  It will be constructed with `ZoneData`,
> and will be constructed by revised `ZoneTable`.
>
> It will still be quite complicated, so it's probably defined in a
> separate .cc file.
>
> It probably makes more sense to move ZoneData::findNode() to finder's
> dedicated subroutine (in an unnamed namespace - it shouldn't have to
> be a member function of the finder).
>
> This task ports the basic part of its find() and findAll().  Skip
> wildcard consideration.  Also just use the base (default) result
> context.
>
> Depend on #2107 and #2108.

New description:

 With #2108, the `InMemoryZoneFinder` can now concentrate on its
 find()-related tasks.  It will be constructed with `ZoneData`,
 and will be constructed by revised `ZoneTable`.

 It will still be quite complicated, so it's probably defined in a
 separate .cc file.

 It probably makes more sense to move ZoneData::findNode() to finder's
 dedicated subroutine (in an unnamed namespace - it shouldn't have to
 be a member function of the finder).

 This task ports the basic part of its find() and findAll().  Skip
 wildcard consideration.  Also just use the base (default) result
 context.

 Resulting `TreeNodeRRset` needs to be created dynamically.  We should
 probably use an object pool.

 Depend on #2107 and #2108.

--

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