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

Comment (by jinmei):

 Replying to [comment:1 vorner]:
 > I don't think that the implicit acquiring and releasing is a problem. Or
 do you
 > mean some other one than it is released when you do wait and acquired
 again
 > before the wait terminates? I think this would work (provided the Mutex
 adds
 > some kind of friend declaration for the condition):

 I meant, by "non trivial extensions," we'd need to do something like
 ugly friend declaration:-)  And, IMO, when `friend` seems to be the
 choice in the first impression, we should generally think about
 whether there can be a cleaner design.  For example, we should check
 what kind of abstraction boost thread is using and should learn from
 it, not just starting from what we have as a given condition.

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