Difference between revisions of "Uno/Binary/Spec/Threading-Architecture"
From Apache OpenOffice Wiki
m (Consisted wording.) |
m (Adapted Links.) |
||
| Line 2: | Line 2: | ||
==Feature== | ==Feature== | ||
| − | 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. | + | 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 components default to be [[Uno/Term/Thread Unsafe|thread-unsafe]]. | * All components default to be [[Uno/Term/Thread Unsafe|thread-unsafe]]. | ||
* All public libraries provide environment free references. | * All public libraries provide environment free references. | ||
Revision as of 08:45, 5 September 2006
Type: Specification State: draft
Feature
The Binary Uno threading-architecture leverages the binary Uno threading-model to implement thread-aware code where necessary only.
- All components default to be thread-unsafe.
- All public libraries provide environment free references.
- All applications default to be thread-unsafe (note: this will only be achievable with implementation environments).
- All components and libraries are thread-transparent.
The following components are specified to be thread-safe:
