BIND 10 #2539: implement InMemoryClient iterator getSOA()

[BIND 10 Development]

#2539: implement InMemoryClient iterator getSOA()
-------------------------------------+-------------------------------------
            Reporter:  vorner        |                        Owner:  kean
                Type:  task          |                       Status:
            Priority:  medium        |  reviewing
           Component:  data source   |                    Milestone:
            Keywords:                |  Sprint-20131015
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DNS           |                 CVSS Scoring:
Estimated Difficulty:  3             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:  muks => kean


Comment:

 Hi Kean

 Is there a use-case for this `getSOA()` optimization?

 The iterator is to be constructed and used where required (it's not a
 long-living object as it requires the underlying datasource to be constant
 during its use). The iterator is mainly for use during zone transfers and
 related serial comparisons. In such places, code that uses it would not
 have to call `getSOA()` multiple times. This optimization would further
 complicate an already complicated iterator for little benefit. It would
 also break the "identical" guarantee of `ZoneIterator::getSOA()` (though
 we assume the underlying data source must not change during iterator use).

 But just in case this is required, can you point out a place where
 `getSOA()` needs to be called multiple times?

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