BIND 10 #1262: AXFR-style IXFR-in protocol handling

[BIND 10 Development]

#1262: AXFR-style IXFR-in protocol handling
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  jinmei                             |                Status:  new
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20111011
  blocker                            |            Resolution:
                  Component:  xfrin  |             Sensitive:  0
                   Keywords:         |           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):

 I've pushed a mostly complete (feature wise) snapshot of #1261 at branch
 trac1261.  There may be some design level dicussions in the implementation
 that can require substantial changes, but if someone is looking for a
 new task related to IXFR, I believe this task can be started on top of
 the current snapshot of trac1261.

 What would have to be done is to update _handle_xfrin_responses()
 so that after calling handle_rr() if the new state is XfrinAXFR
 switch to the existing sqlite3-specific AXFR code (which will have
 to be adjusted a bit to support the both cases).  Of course,
 this is intended to be a short term workaround, and the AXFR
 part should also be integrated to the new code.  (Or if it's
 deemed to be easy at this point, we may be able to complete that
 part within this sprint).

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