Difference between revisions of "Uno/Binary/Spec/Threading-Model"

Revision as of 11:17, 18 April 2006

author: Kr
version: 8181
state: draft
created: 01/10/2006
changed: 03/06/2006
type: specification

Binary UNO

Threading Model

Feature

UNO Threading Model for the Binary UNO runtime.

Support thread model specific compilation. The following new defines select the UNO threading model 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.

Associated environments are:

• UNO_THREAD_SAFE => "<ABI>"
• UNO_THREAD_UNSAFE => "<ABI>:mutex"
• UNO_THREAD_AFFINE => "<ABI>:thread"

Threading model specific environments are backed by the appropriate purpose environments.

• "<ABI>:mutex" is backed by the default mutex environment
• "<ABI>" is backed by the default free environment (as usual)
• "<ABI>:thread" is backed by the default thread environment

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, the 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 Extensions

• Environment Guards
• Environment Aware References
• Environment Stacks
• Cascaded Mappings
• Purpose Environments

Dependencies

• Environment Guards
• Environment Aware References
• Environment Stacks
• Cascaded Mappings
• Purpose Environments

Compatibility Issues

• Environment Guards
• Environment Aware References
• Environment Stacks
• Cascaded Mappings
• Purpose Environments