BIND 10 #2234: staged zone reloading to in-memory

[BIND 10 Development]

#2234: staged zone reloading to in-memory
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  jinmei                             |                Status:  new
                       Type:  task   |             Milestone:  Next-Sprint-
                   Priority:         |  Proposed
  medium                             |            Resolution:
                  Component:  data   |             Sensitive:  0
  source                             |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
  background zone loading            |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by muks):

 Right now, `InMemoryClient::load()` loads the zone and also sets it into
 the `ZoneTable`. The setting is done by swapping an existing `ZoneData`
 with a new one, and destroying the old one after that. Code outside
 `InMemoryClient` cannot access the `ZoneData` between the loading and
 setting in the `ZoneTable`. But because this swapping of `ZoneData` to the
 `ZoneTable` is a single operation done after the zone is completely
 loaded, I think we can continue using that if `InMemoryClient::load()` is
 called in a separate thread. The existing `ZoneTable` will contain the old
 data right upto the point the new `ZoneData` is swapped in.

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