BIND 10 #1212: Implement IXFR-in

[BIND 10 Development]

#1212: Implement IXFR-in
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  stephen                            |                Status:  new
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20111011
  blocker                            |            Resolution:
                  Component:  xfrin  |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  N/A    |  Estimated Difficulty:  12
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jelte):

 In general this looks like a reasonable breakdown.

 I do wonder about the commit-per-100-'diffs' though, but maybe i
 misunderstand that specific part of your description. One per soa->soa I
 can understand (as this reflects one complete change), but doing
 intermediate commits may leave the zone in an inconsistent state even
 without a second writer (if there is a failure after it). OTOH if we don't
 have onle one big transaction it may protect us from those, but one might
 run into global database transaction timeouts...

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