BIND 10 #817: Combining/refactoring SQLite/in-memory data source

[BIND 10 Development]

#817: Combining/refactoring SQLite/in-memory data source
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  stephen                            |                Status:  accepted
                       Type:         |             Milestone:
  enhancement                        |  Sprint-20110614
                   Priority:  major  |            Resolution:
                  Component:  data   |             Sensitive:  0
  source                             |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  14.0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 See the proposed refactored data source design on the wiki page:
 http://bind10.isc.org/wiki/DataSourceDesign

 And, for the main subject of this ticket, I'd propose option b:

   b. Introduce the refactored data source, then update the writable data
 sources to match the new design.

 because, if we agree on the basic concept of the refactoring, the
 resulting interface of the writability would need to be substantially
 rewritten anyway.  Some part of the code logic in the trac374 branch
 (such as that for IXFR or dynamic update) may be reused later.

 My suggestion for the next step of this ticket is to move it to the
 review queue just as a placeholder while we discuss the data source
 design at the bind10-dev list, and then close it at (around) the end
 of this sprint (or even before that if the higher level discussion
 converges sooner).

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