Difference between revisions of "Spec/Threading-Model"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (Fixed section indention, some wording.)
Line 2: Line 2:
 
Status:  final<br>
 
Status:  final<br>
  
−
==The OOo Threading Model==
+
==Description==
−
===Description===
+
According to the [[Architecture/Threading|goals]] for the OOo threading-model, the OOo threading-model has to support the following 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|thread-affine]],
−
* [[Uno/Term/Thread Affine|thread affine]]
+
* [[Uno/Term/Thread Safe|thread-safe]], and
−
* [[Uno/Term/Thread Safe|thread safe]]
+
* [[Uno/Term/Thread Unsafe|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]], 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
−
* UNO APIs have to be implemented thread safe  
+
* Uno APIs have to be implemented [[Uno/Term/Thread Safe|thread-safe]],
−
* UNO APIs have to be implemented thread transparent  
+
* Uno APIs have to be implemented [[Uno/Term/Thread Transparent|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|thread affine]]
+
** [[Uno/Term/Thread Affine|thread-affine]],
−
** [[Uno/Term/Thread Safe|thread safe]]
+
** [[Uno/Term/Thread Safe|thread-safe]], or
−
** [[Uno/Term/Thread Unsafe|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]].
+
It is proposed, the OOo threading-model to be the [[Uno/Spec/Threading Model|Uno threading-model]].
  
−
===Dependencies===
+
==Dependencies==
 
* [[Uno/Spec/Threading Model]]
 
* [[Uno/Spec/Threading Model]]
  
  
 
[[Category:Spec]]
 
[[Category:Spec]]

Revision as of 10:52, 4 September 2006

Type: Specification
Status: final

Description

According to the goals for the OOo threading-model, the OOo threading-model has to support the following 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, OOo just being a set of Uno components.

The rules for Uno in respect to threading, basically repeating the threading-model goals, are

It is proposed, the OOo threading-model to be the Uno threading-model.

Dependencies

Personal tools