BIND 10 #2205: introduce a "data source configurator" thread in auth

[BIND 10 Development]

#2205: introduce a "data source configurator" thread in auth
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  jinmei                             |                Status:  new
                       Type:  task   |             Milestone:  Next-Sprint-
                   Priority:         |  Proposed
  medium                             |            Resolution:
                  Component:         |             Sensitive:  0
  b10-auth                           |           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      |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * estimatedhours:  7 => 0


Comment:

 Maybe it's a bit of haskellism on my side, but whenever I do something
 like this, the easiest (and most generic) approach is creating a work
 thread with a queue of functions (or functors) ‒ something like a wrapper
 around a thread, conditional variable and `vector<boost::function<void()>
 >`.

 It is simple, generic and the code that needs to be backgrounded (like the
 loading we plan) doesn't have to be split across multiple places ‒ the
 code that needs something done in the background contains the functor as
 well.

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