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:
                   Priority:         |  Sprint-20120918
  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 jinmei):

 Replying to [comment:1 muks]:
 > [...] 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.

 Maybe I don't fully understand this, but I believe the "swapping" must
 be in a critical section protected by a lock.  So unless we add the
 lock within the load() method we should have a separate interface for
 swapping.  And, for the same reason, we should have a separate
 interface for the cleanup.

 See also #2235.

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