Difference between revisions of "Uno/Spec/Threading-Architecture"
From Apache OpenOffice Wiki
m (Wording.) |
m (Fixed categories.) |
||
| Line 16: | Line 16: | ||
| + | [[Category:Draft]] | ||
| + | [[Category:Spec]] | ||
| + | [[Category:Uno]] | ||
[[Category:Uno:Spec]] | [[Category:Uno:Spec]] | ||
| − | |||
Latest revision as of 08:37, 29 November 2006
Type: Specification State: draft
Umbrella specification regarding when to use which thread related construct in Uno implementations.
APIs
- When implementing fast APIs, use threads for accessing slow APIs. Do notify about completion asynchronously.
- Be conservative, only program thread related / aware where necessary.
- Implement public libraries APIs etc. as wide as the parameters (e.g. always return appropriate purpose objects in case of OBI specialization)
- Implement public APIs thread-transparent.
- Only program thread-safe, if parallelism is required (e.g. for interrupting a method call).
- Encapsulate thread-affinity.
- Enable concurrent access to inter-thread objects (avoiding bottlenecks).
