Difference between revisions of "Spec/Threading-Architecture"
From Apache OpenOffice Wiki
m (→Dependencies: Adapted link.) |
m (Adapted Link.) |
||
Line 2: | Line 2: | ||
State: draft <br> | State: draft <br> | ||
− | The OOo Threading Architecture leverages [[Spec/Threading Model|OOos]] respectively [[Uno/Spec/Threading Model|Unos]] threading-model to implement [[Uno/Term/Thread Aware|thread-aware]] code where necessary only. | + | The OOo Threading Architecture leverages [[Spec/Threading-Model|OOos]] respectively [[Uno/Spec/Threading Model|Unos]] threading-model to implement [[Uno/Term/Thread Aware|thread-aware]] code where necessary only. |
==Principles== | ==Principles== |
Revision as of 15:48, 4 September 2006
Type: Specification
State: draft
The OOo Threading Architecture leverages OOos respectively Unos threading-model to implement thread-aware code where necessary only.
Principles
Principles of the threading-architecture are
- all components, libraries and applications default to be thread-unsafe, with only a few well motivated exceptions (being thread-safe, thread-affine,
- all office code is specified to be thread-transparent.
Thread-Safe
The following modules are specified to be thread-safe:
- UCB (Universal Content Broker) Component - ucb/ucb
- UCB Helper Library - ucb/ucbhelper
- Config Manager Components - util/configmgr
- Package Manager - framework/desktop/source/pkgchk
- The office connection acceptor (server) component in the desktop project.
Thread-Affine
The following modules are specified to be thread-affine:
- DDE (Dynamic Data Exchange) - util/source/svdde/svtools
- Windows Clipboard Component - gsl/dtrans/source/win32/clipbe
- Windows Drag&Drop Component - gsl/dtrans/source/win32/dnd