Difference between revisions of "Uno/Binary/Spec/Threading-Model"
From Apache OpenOffice Wiki
m |
(Fixed dependencies and API.) |
||
Line 8: | Line 8: | ||
: The [[Uno/Spec/Threading Model]] for the Binary UNO runtime. | : The [[Uno/Spec/Threading Model]] for the Binary UNO runtime. | ||
: | : | ||
− | : Support threading type specific compilation. | + | : Support threading type specific compilation via <code>#define</code>. Specify defines for the following threading types: |
− | :* | + | :* thread unsafe |
− | :* | + | :* thread safe |
− | :* | + | :* thread affine |
+ | :* thread free | ||
: | : | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
: Threading model specific environments are backed by the appropriate purpose environments. | : Threading model specific environments are backed by the appropriate purpose environments. | ||
:* <code>"<ABI>:unsafe" </code> is backed by the default [[Uno/Binary/Spec/Thread Unsafety Bridge]]. | :* <code>"<ABI>:unsafe" </code> is backed by the default [[Uno/Binary/Spec/Thread Unsafety Bridge]]. | ||
Line 28: | Line 22: | ||
; Rationale | ; Rationale | ||
− | : The current threading related code quality of OOo has proven | + | : The current threading related code quality of OOo has proven that doing proper multi threading programming is not easy. Even seemingly simple things, as thread safeness, seem to be unreachable. Therefor UNO programming must be as simple as possible in respect to multi threading programming. |
− | ; API | + | ; API: |
− | :* | + | :The following new defines select the threading type for binary UNO: |
− | :* | + | :* <code>UNO_THREAD_SAFE</code> |
− | :* | + | :* <code>UNO_THREAD_UNSAFE</code> |
− | :* | + | :* <code>UNO_THREAD_AFFINE</code> |
− | :* | + | : |
+ | :Services / Client code compiled with one of these defines lifes in the associated environment. Not defining one of these defines, lets binary UNO fall back to <code>CPPU_THREAD_SAFE</code>, and gives a warning. This is compatible with the original behaviour. | ||
+ | |||
+ | : The Associated environments are: | ||
+ | :* <code>UNO_THREAD_SAFE </code> => <code>"<ABI>"</code> | ||
+ | :* <code>UNO_THREAD_UNSAFE</code> => <code>"<ABI>:unsafe"</code> | ||
+ | :* <code>UNO_THREAD_AFFINE</code> => <code>"<ABI>:affine"</code>, see [[Uno/Binary/Spec/Thread Affinity Bridge]] for details. | ||
; Dependencies: | ; Dependencies: | ||
+ | :* [[Uno/Binary/Spec/Thread Unsafety Bridge]] | ||
+ | :* [[Uno/Binary/Spec/Thread Affinity Bridge]] | ||
+ | :* [[Uno/Binary/Spec/Implementation Environment]] | ||
+ | :* [[Uno/Binary/Spec/Environment Stack]] | ||
+ | :* [[Uno/Binary/Spec/Cascaded Mapping]] | ||
+ | :* [[Uno/Binary/Spec/Purpose Environments]] | ||
+ | :* [[Uno/Binary/Spec/Environment Substitution]] | ||
:* Environment Guards | :* Environment Guards | ||
:* Environment Aware References | :* Environment Aware References | ||
− | |||
− | |||
− | |||
− | ; Compatibility Issues: | + | ; Compatibility Issues: None. |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
[[Category:Uno:Binary:Spec]] | [[Category:Uno:Binary:Spec]] |
Revision as of 14:30, 19 April 2006
version: 8568
state: draft
type: specification
Threading Model
- Feature
- The Uno/Spec/Threading Model for the Binary UNO runtime.
- Support threading type specific compilation via
#define
. Specify defines for the following threading types:- thread unsafe
- thread safe
- thread affine
- thread free
- Threading model specific environments are backed by the appropriate purpose environments.
-
"<ABI>:unsafe"
is backed by the default Uno/Binary/Spec/Thread Unsafety Bridge. -
"<ABI>"
is backed by the default thread safe environment (as usual). -
"<ABI>:thread"
is backed by the default is backed by the default Uno/Binary/Spec/Thread Affinity Bridge.
-
- The UNO Threading Model specification for Binary UNO is the sum of the specifications for the parts, see below for details.
- Rationale
- The current threading related code quality of OOo has proven that doing proper multi threading programming is not easy. Even seemingly simple things, as thread safeness, seem to be unreachable. Therefor UNO programming must be as simple as possible in respect to multi threading programming.
- API
- The following new defines select the threading type for binary UNO:
-
UNO_THREAD_SAFE
-
UNO_THREAD_UNSAFE
-
UNO_THREAD_AFFINE
-
- Services / Client code compiled with one of these defines lifes in the associated environment. Not defining one of these defines, lets binary UNO fall back to
CPPU_THREAD_SAFE
, and gives a warning. This is compatible with the original behaviour.
- The Associated environments are:
-
UNO_THREAD_SAFE
=>"<ABI>"
-
UNO_THREAD_UNSAFE
=>"<ABI>:unsafe"
-
UNO_THREAD_AFFINE
=>"<ABI>:affine"
, see Uno/Binary/Spec/Thread Affinity Bridge for details.
-
- Dependencies
-
- Uno/Binary/Spec/Thread Unsafety Bridge
- Uno/Binary/Spec/Thread Affinity Bridge
- Uno/Binary/Spec/Implementation Environment
- Uno/Binary/Spec/Environment Stack
- Uno/Binary/Spec/Cascaded Mapping
- Uno/Binary/Spec/Purpose Environments
- Uno/Binary/Spec/Environment Substitution
- Environment Guards
- Environment Aware References
- Compatibility Issues
- None.