BIND 10 #1810: support NO_WILDCARD option in InMemoryZoneFinder::find().

[BIND 10 Development]

#1810: support NO_WILDCARD option in InMemoryZoneFinder::find().
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jelte
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20120515
  medium                             |            Resolution:
                  Component:  data   |             Sensitive:  0
  source                             |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  3
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:  in-    |
  memory NSEC                        |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:9 jinmei]:
 > Replying to [comment:8 jelte]:
 > > The change looks simple & okay.
 > >
 > > I am wondering if there is a hidden semantical conflict with 1808
 though :) Or maybe just an oversight; the DATASRC_MEM_NXRRSET either also
 needs some form of NO_WILDCARD check, or maybe it simply should never
 rename its result; when I merge all branches together I get a wildcard-
 expanded NSEC record in my responses.

 Okay, I now (believe I) understand what you meant, which should be this:
 http://bind10.isc.org/ticket/1808#comment:12
 and you're right.  We should address it in #1808.

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