BIND 10 #2332: define and implement wrapper interface for conditional variables

[BIND 10 Development]

#2332: define and implement wrapper interface for conditional variables
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  jinmei                             |                Status:  accepted
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20121023
  medium                             |            Resolution:
                  Component:         |             Sensitive:  0
  b10-auth                           |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  5
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
  background zone loading            |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 So, trac2332 is ready for review.

 The main code is not big and shouldn't be difficult to review.

 I made a few unrelated (piggy-backed) cleanups.  In particular,
 dc5492b may not look trivial.  See the commit log.

 If the content of the branch is okay, I'd like to propose changing the
 file name "lock.h/cc" to something like sync.h/cc or
 synchronization.h/cc.  While condition variables are also used with
 locks, locks are secondary concept for condition variables (at least
 condvar can exist without a lock).  Having all of these, I believe a
 higher level concept "sync(hronization)" is a better file name.

 But I didn't make this change in the branch yet to keep the diff
 minimal.

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