Difference between revisions of "Uno/Binary/Spec/Threading-Architecture"
From Apache OpenOffice Wiki
(Specification of the Binary UNO Threading Architecture.) |
|||
(13 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | + | Type: Specification State: draft | |
− | State: | + | |
− | + | ||
− | + | Refinement of the [[Uno/Spec/Threading-Architecture|Uno threading-architecture specification]] for [[Uno/Binary|Binary Uno]]. | |
− | + | ==API== | |
− | :* All | + | The [[Uno/Binary|Binary Uno]] threading-architecture leverages the [[Uno/Binary/Spec/Threading-Model|Binary Uno threading-model]] to implement [[Uno/Term/Thread Aware|thread-aware]] code where necessary only: |
− | + | * All implementations default to [[Uno/Term/Thread Unsafe|thread-unsafe]]. | |
− | + | * All public libraries are [[Uno/Term/Object Binary Interface|OBI]] specialized. | |
− | + | * All public libraries provide appropriate objects (objects matching the clients environment). | |
− | + | * All APIs are [[Uno/Term/Thread Transparent|thread-transparent]]. | |
− | + | ||
− | + | ||
− | + | The following components are specified to be [[Uno/Term/Thread Safe|thread-safe]]: | |
+ | * {{Uno/UDKlink|io/source/acceptor|util}} - requires parallelism to enable abortion. | ||
− | + | ==Dependencies== | |
− | + | * [[Uno/Spec/Threading-Architecture]] | |
+ | * [[Uno/Binary/Spec/Threading-Model]] | ||
− | [[Category:Uno:Binary: | + | [[Category:Spec]] |
+ | [[Category:Uno]] | ||
+ | [[Category:Uno:Binary]] | ||
+ | [[Category:Draft]] | ||
+ | [[Category:Multi-Threading]] |
Latest revision as of 07:14, 19 June 2007
Type: Specification State: draft
Refinement of the Uno threading-architecture specification for Binary Uno.
API
The Binary Uno threading-architecture leverages the Binary Uno threading-model to implement thread-aware code where necessary only:
- All implementations default to thread-unsafe.
- All public libraries are OBI specialized.
- All public libraries provide appropriate objects (objects matching the clients environment).
- All APIs are thread-transparent.
The following components are specified to be thread-safe:
- util/io/source/acceptor - requires parallelism to enable abortion.