BIND 10 #1911: document how to configure in-memory data source with sqlite3 backend

[BIND 10 Development]

#1911: document how to configure in-memory data source with sqlite3 backend
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20120515
  medium                             |            Resolution:
                  Component:         |             Sensitive:  0
  documentation                      |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  3
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:  xfr    |
  for in-memory                      |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:  muks => jinmei


Comment:

 Hi jinmei

 Replying to [comment:3 jinmei]:
 > About "Incoming Transfers with In-memory Datasource":
 >
 > The "incoming zone" in "In the case of an incoming zone" sounds
 > awkward, that is, what's "incoming zone"?  Do you mean "incoming zone
 > transfer" (but then "which is served..." doesn't make much sense)?  Or
 > maybe it should be "secondary zone"?  I think this sentence should be
 > clarified.

 This text has been updated now.

 > I'd also clarify what the administrator should do (or doesn't have to)
 > if they want to serve a zone from in-memory for normal queries while
 > updating it by incoming zone transfers.

 I don't follow this. Can you say what you want to see?

-- 
Ticket URL: <http://149.20.48.40/ticket/1911#comment:5>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development