BIND 10 #2198: make sure InterprocessSyncLocker is thread safe

[BIND 10 Development]

#2198: make sure InterprocessSyncLocker is thread safe
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  vorner
  jinmei                             |                Status:  reviewing
                       Type:         |             Milestone:
  defect                             |  Sprint-20121023
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  Core
  logging                            |  Estimated Difficulty:  5
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:  muks => vorner


Comment:

 Hi vorner

 To move this bug forward, I've used the `Mutex::Locker` and made the
 `Mutex` operations private again. I've used a `shared_ptr` instead of a
 `scoped_ptr`, and the ref is then retained by the class member.

 If you want to rewrite this, please feel free and assign this bug to
 yourself.

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