|
|
| (15 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | author: [[User:Kr|Kr]] <br>
| + | Type: Specification State: Evolving Availability: URE 1.3 (SRC680_m212) |
| − | version: {{REVISIONID}} <br>
| + | |
| − | state: draft <br>
| + | |
| − | created: 01/17/2006 <br>
| + | |
| − | type: specification <br>
| + | |
| | | | |
| − | == Binary UNO ==
| + | The [[Uno/Spec/Thread Affinity Bridge]] for [[Uno/Binary|Binary Uno]]. |
| − | === Thread Affine Environment ===
| + | |
| | | | |
| − | ; Description
| + | ==API== |
| − | : The Thread Affine Environment protects thread affine objects from being called by the wrong threads. It does this by providing a dedicated thread, into which it delegates the calls prior to invocation. This dedicated thread is therefor the thread any objects create an affinity to.
| + | A [[Uno/Spec/Purpose Bridge]] named |
| | + | <code>"affine_uno_uno"</code> |
| | | | |
| − | ; Feature:
| + | ==Dependencies== |
| − | : A purpose environment protecting thread affine objects:
| + | * [[Uno/Spec/Environment Stack]] |
| − | : - enter: Associates the current thread with the environment
| + | * [[Uno/Spec/Thread Affinity Bridge]] |
| − | : - leave: An case no objects are mapped it disassociates the current thread with the environment, in case objects are mapped and this is the last leave, it blocks until no objects are mapped anymore.
| + | |
| − | :
| + | |
| − | : - callInto: Calls the desired method from the associated thread.
| + | |
| − | : - callOut: Calls the desired method from the outer thread, if there is no outer thread yet, the associated thread is used.
| + | |
| | | | |
| − | ; Rationale
| |
| − | : Some APIs have thread affinities in respect to particular handles they return. For exmaple, on Win32 the window create, destroy and message functions require to be called by the same thread which actually created the window. This thread affinity is inherited when developing APIs on top of these thread affinie APIs.
| |
| − | : In general, thread affine APIs are hard to program, especially in generic frameworks where it is not knowable before hand how long a thread lives and on whichs objects it calls.
| |
| | | | |
| − | ; API
| + | [[Category:Draft]] |
| − | | + | [[Category:Spec]] |
| − | ; Compatibility Issues: None.
| + | [[Category:Uno]] |
| − | | + | [[Category:Uno:Binary]] |
| − | ; Dependencies:
| + | [[Category:Multi-Threading]] |
| − | :* EnvStack | + | |
| − | | + | |
| − | [[Category:Uno:Spec]] | + | |
