BIND 10 #1894: use labelsequence in findNSEC3

[BIND 10 Development]

#1894: use labelsequence in findNSEC3
-------------------------------------+-------------------------------------
            Reporter:  jelte         |                        Owner:  muks
                Type:  enhancement   |                       Status:
            Priority:  high          |  closed
           Component:  Unclassified  |                    Milestone:
            Keywords:                |  bind10-1.2-release-freeze
           Sensitive:  0             |                   Resolution:  fixed
         Sub-Project:  DNS           |                 CVSS Scoring:
Estimated Difficulty:  5             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by muks):

 * status:  reviewing => closed
 * resolution:   => fixed


Comment:

 Merged to `master` branch in commit
 `fe7ae0a7b3eca38b81779b9cad22161e4bcf1d26`:
 {{{
 * 7c1e2ec [1894] Minor coding style fix
 * f2ce3de [1894] Avoid doing costly name splits (database backend)
 * 498b511 [1894] Add missing method
 * aff22ac [1894] Use a single LabelSequence object instead of doing costly
 name splits
 * 4aef41d [1894] Add LabelSequence version of NSEC3Hash::calculate()
 * e29050c [1894] Avoid expensive Name copy
 }}}

 There was a merge conflict, but the exact code that was the result of the
 resolution has been reviewed in this ticket.

 Resolving as fixed. Thank you for the reviews Paul.

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