Difference between revisions of "Uno/Binary/Impl/Thread Affinity Bridge"
From Apache OpenOffice Wiki
| (8 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | Type: Implementation State: Finished Availability: URE 1.3 (SRC680_m212) | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | Implementation of [[../../Spec/Thread Affinity Bridge]]. | |
| − | + | ||
| − | + | ==Description== | |
| + | The Thread Affinity Bridge ensures that [[../Thread Affine|thread affine]] objects are always called by the same thread. | ||
| − | + | It does this by using a private thread, to which it switches prior actually invoking a particular object. This private thread is therefore the thread objects may create an [[Uno/Term/Thread Affine|affinity]] to. The [[Uno/Term/Thread Affine|affinity]] also switches back to the originator thread, in case an object tries to call out, this ensures [[Uno/Term/Thread Transparent|thread transparency]]. | |
| − | + | The Affinity Bridge behaves as follows, | |
| + | * entering a Thread Affine environment associates the current thread with it, in case the environment already has a thread associated, the enter blocks until no object is registered any more, | ||
| + | * leaving a Thread Affine environment disassociates the current thread from the [[Uno/Spec/Environment|Environment]], in case objects are still mapped, the leave blocks until no object is registered any more, | ||
| + | * calling into the Thread Affinity environment, leads to the invocation of the passed function by the associated thread, | ||
| + | * calling out of the Thread Affinity environment, leads to the invocation of the passed function by the in-calling thread, in case of no in-calling thread, the associated thread calls out directly. | ||
| − | + | ==Files== | |
| + | * {{Uno/UDKlink|cppu/source/AffineBridge/ThreadEnvironment.cxx}} | ||
| + | * {{Uno/UDKlink|cppu/source/AffineBridge/makefile.mk}} | ||
| − | + | ==Tests== | |
| − | + | * [[../../Test/Thread Affinity Bridge]] | |
| − | + | ||
| − | + | ||
| − | + | ==Dependencies== | |
| − | + | * [[../Environment Stack]] | |
| − | + | * [[../Runtime]] | |
| − | : | + | * [[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 Uno/Binary/Spec/Thread Affinity Bridge.
Contents
Description
The Thread Affinity Bridge ensures that thread affine objects are always called by the same thread.
It does this by using a private thread, to which it switches prior actually invoking a particular object. This private thread is therefore the thread objects may create an affinity to. The affinity also switches back to the originator thread, in case an object tries to call out, this ensures thread transparency.
The Affinity Bridge behaves as follows,
- entering a Thread Affine environment associates the current thread with it, in case the environment already has a thread associated, the enter blocks until no object is registered any more,
- leaving a Thread Affine environment disassociates the current thread from the Environment, in case objects are still mapped, the leave blocks until no object is registered any more,
- calling into the Thread Affinity environment, leads to the invocation of the passed function by the associated thread,
- calling out of the Thread Affinity environment, leads to the invocation of the passed function by the in-calling thread, in case of no in-calling thread, the associated thread calls out directly.
