Difference between revisions of "Spec/Threading-Model"
From Apache OpenOffice Wiki
(state changed.) |
m (Fixed type field.) |
||
| Line 1: | Line 1: | ||
| − | Type: | + | Type: Specification<br> |
Status: final<br> | Status: final<br> | ||
| − | Author: | + | Author: Kai Sommerfeld, Kay Ramme |
| − | == The OOo Threading Model == | + | ==The OOo Threading Model== |
According to the [[Architecture/Threading|goals]] for the OOo Threading Model, the OOo Threading Model has to support three threading types: | According to the [[Architecture/Threading|goals]] for the OOo Threading Model, the OOo Threading Model has to support three threading types: | ||
| − | * [[Uno/Term/Thread Affine | | + | * [[Uno/Term/Thread Affine|thread affine]] |
| − | * [[Uno/Term/Thread Safe | | + | * [[Uno/Term/Thread Safe|thread safe]] |
| − | * [[Uno/Term/Thread Unsafe | | + | * [[Uno/Term/Thread Unsafe|thread unsafe]] |
| − | Every of these types could be implemented with the help of libraries etc., the most simple and elegant solution seems to be the extension of the [[Uno/Binary | Binary UNO Runtime]], ideally supporting the declaration of the threading model to be used. | + | Every of these types could be implemented with the help of libraries etc., the most simple and elegant solution seems to be the extension of the [[Uno/Binary|Binary UNO Runtime]], ideally supporting the declaration of the threading model to be used. |
| − | This means, that the OOo threading model is going to be the [[Uno/Spec/Threading Model | UNO Threading Model]], which also fits with the [[Architecture/OOo as UNO Components | vision]], of OOo just being a set of UNO components. | + | This means, that the OOo threading model is going to be the [[Uno/Spec/Threading Model|UNO Threading Model]], which also fits with the [[Architecture/OOo as UNO Components|vision]], of OOo just being a set of UNO components. |
The rules for UNO in respect to threading, basically repeating the threading model goals, are: | The rules for UNO in respect to threading, basically repeating the threading model goals, are: | ||
| Line 18: | Line 18: | ||
* UNO APIs have to be implemented thread transparent | * UNO APIs have to be implemented thread transparent | ||
* Code has to be implemented following one of three threading approaches (addressing (d),(f)): | * Code has to be implemented following one of three threading approaches (addressing (d),(f)): | ||
| − | ** [[Uno/Term/Thread Affine | | + | ** [[Uno/Term/Thread Affine|thread affine]] |
| − | ** [[Uno/Term/Thread Safe | | + | ** [[Uno/Term/Thread Safe|thread safe]] |
| − | ** [[Uno/Term/Thread Unsafe | | + | ** [[Uno/Term/Thread Unsafe|thread unsafe]] |
| + | |||
| + | It is proposed, the OOo Threading Model to be the [[Uno/Spec/Threading Model|UNO Threading Model]]. | ||
| − | |||
[[Category:Spec]] | [[Category:Spec]] | ||
Revision as of 07:29, 10 July 2006
Type: Specification
Status: final
Author: Kai Sommerfeld, Kay Ramme
The OOo Threading Model
According to the goals for the OOo Threading Model, the OOo Threading Model has to support three threading types:
Every of these types could be implemented with the help of libraries etc., the most simple and elegant solution seems to be the extension of the Binary UNO Runtime, ideally supporting the declaration of the threading model to be used.
This means, that the OOo threading model is going to be the UNO Threading Model, which also fits with the vision, of OOo just being a set of UNO components.
The rules for UNO in respect to threading, basically repeating the threading model goals, are:
- UNO APIs have to be implemented thread safe
- UNO APIs have to be implemented thread transparent
- Code has to be implemented following one of three threading approaches (addressing (d),(f)):
It is proposed, the OOo Threading Model to be the UNO Threading Model.