BIND 10 #1331: Extend the ZoneUpdater class to support adding diffs

[BIND 10 Development]

#1331: Extend the ZoneUpdater class to support adding diffs
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:  major  |  Sprint-20111122
                  Component:  data   |            Resolution:
  source                             |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  N/A    |  Estimated Difficulty:  4
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:         |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => jinmei


Comment:

 Hello

 Replying to [comment:16 jinmei]:
 > If the sequence requirement is a must, what's the point of the
 > "flexibility" of not doing the check?  That just seems to be laziness
 > that naively trusts the application does the right thing.

 As discussed on jabber, my intention was to allow the lazy backends, but
 as discussed, I strengthened the requirement and it „will“ instead of
 „might“ now.

 I also discovered I forgot to commit a test change, so it got lost. It is
 there now.

 > > He says he would like one. So, something like this?
 > >
 > > {{{
 > > [func]
 > > The database data sources can now store diffs when updating the data.
 > > }}}
 >
 > We actually also extend the top level interface.  I'd mention that,
 > e.g.:
 > {{{
 > 317.? [func]
 >       datasrc: the getUpdater (and get_updater for python) method of
 >       DataSourceClient supports an optional 'journaling' parameter to
 >       indicate the generated updater to store diffs.  The database based
 >       derived class implements this extension.
 > }}}

 Is the python interface update supposed to be part of this ticket? If so,
 I should add it, because this ticket handles the C++ part only.

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