BIND 10 #2309: define ZoneFinder::findAtOrigin()

[BIND 10 Development]

#2309: define ZoneFinder::findAtOrigin()
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  task          |                       Status:  new
            Priority:  medium        |                    Milestone:  Next-
           Component:  data source   |  Sprint-Proposed
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:7 vorner]:
 > Should the option work for `findAtOrigin` only, or generally for `find`?

 For completeness, I think it should (otherwise it'd be confusing),
 although it's not necessarily needed for the minimum goal in this
 context.

 > When the return value is the same, would abusing usual `find` with a
 hint-option work? Something like `find(origin, type, options |
 IS_ORIGIN)`? The data sources that don't have this optimisation would just
 ignore the option, while the optimised ones could ignore the name.

 Unfortunately not, because the specific motivation of `findAtOrigin()`
 is that the caller doesn't have to get a `Name` object of the zone
 origin.  It involves dynamic creation of the object for in-memory
 data source, which is generally expensive.

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