Difference between revisions of "Uno/Binary/Impl/Thread Unsafety Bridge"
From Apache OpenOffice Wiki
m (Added links. updated.) |
|||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | Type: Implementation State: Finished Availability: URE 1.3 (SRC680_m212) | |
| − | + | ||
| − | + | ||
| − | + | Implementation of the [[Uno/Binary/Spec/Thread Unsafety Bridge]]. | |
| − | + | ==Description== | |
| − | + | The unsafe purpose bridge for [[Uno/Binary|binary Uno]] is implemented by deriving it from the [[Uno/Cpp/Spec/Purpose_Bridge_Implementation_Helper|Purpose Bridge Implementation Helper]] and adding a MutEx as a member. | |
| − | + | The MutEx gets | |
| − | + | * acquired when entering the environment or calling into it, | |
| − | + | * released when leaving the environment, | |
| + | calling out of the environment keeps the MutEx acquired and therefore does not allow another thread to enter it meanwhile. | ||
| + | The MutEx is a SAL MutEx and can be acquired respectively needs to be released multiple times by the same thread. | ||
| − | + | ==Files== | |
| − | + | * {{Uno/UDKlink|cppu/source/UnsafeBridge/UnsafeBridge.cxx}} | |
| − | + | * {{Uno/UDKlink|cppu/source/UnsafeBridge/makefile.mk}} | |
| − | + | ||
| − | [[Category:Uno:Binary: | + | ==Tests== |
| + | * [[../../Test/Thread Unsafety Bridge]] | ||
| + | |||
| + | ==Dependencies== | ||
| + | * [[Uno/Binary/Impl/Environment Stack]] | ||
| + | * [[Uno/Cpp/Spec/Purpose_Bridge_Implementation_Helper]] | ||
| + | |||
| + | |||
| + | [[Category:Impl]] | ||
| + | [[Category:Module:CPPU]] | ||
| + | [[Category:Uno]] | ||
| + | [[Category:Uno:Binary]] | ||
| + | [[Category:Multi-Threading]] | ||
Latest revision as of 07:22, 19 June 2007
Type: Implementation State: Finished Availability: URE 1.3 (SRC680_m212)
Implementation of the Uno/Binary/Spec/Thread Unsafety Bridge.
Contents
Description
The unsafe purpose bridge for binary Uno is implemented by deriving it from the Purpose Bridge Implementation Helper and adding a MutEx as a member.
The MutEx gets
- acquired when entering the environment or calling into it,
- released when leaving the environment,
calling out of the environment keeps the MutEx acquired and therefore does not allow another thread to enter it meanwhile. The MutEx is a SAL MutEx and can be acquired respectively needs to be released multiple times by the same thread.
