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:  UnAssigned
  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      |
-------------------------------------+-------------------------------------

Comment (by 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.

 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.

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