Difference between revisions of "Uno/Effort/Binary/Extend Threading-Model"
m (→Solution: Fixed links.) |
m (→Tasks: Removed unrelated tasks.) |
||
| Line 27: | Line 27: | ||
|- | |- | ||
| [[Uno/Binary|Binary Uno]] || [[Uno/Effort/Binary/Adapt Threading-Architecture|Adapt Threading Architecture]] || 90% || UTF2 | | [[Uno/Binary|Binary Uno]] || [[Uno/Effort/Binary/Adapt Threading-Architecture|Adapt Threading Architecture]] || 90% || UTF2 | ||
| − | |||
| − | |||
|- | |- | ||
| [[Uno/Binary|Binary Uno]] || [[Uno/Effort/Binary/Implement Environment Stack Support]] || 50% || UTF2 | | [[Uno/Binary|Binary Uno]] || [[Uno/Effort/Binary/Implement Environment Stack Support]] || 50% || UTF2 | ||
| − | |||
| − | |||
|- | |- | ||
| [[Uno/Binary|Binary Uno]] || [[Uno/Effort/Binary/Purpose Bridge Tester|Purpose Bridge Tester]] || 80% || UTF2 | | [[Uno/Binary|Binary Uno]] || [[Uno/Effort/Binary/Purpose Bridge Tester|Purpose Bridge Tester]] || 80% || UTF2 | ||
| Line 41: | Line 37: | ||
|- | |- | ||
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Impl/Purpose Bridge Implementation Helper|Purpose Bridge Implementation Helper]] || 100% || UTF2 | | [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Impl/Purpose Bridge Implementation Helper|Purpose Bridge Implementation Helper]] || 100% || UTF2 | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|} | |} | ||
Revision as of 12:23, 7 September 2006
Type: effort Status: in progress(UTF2) Owner: Kay Ramme, [1]
The mission of the Uno threading framework is, to provide a way to design an applications threading-architecture independent of the implementation. This can be described as transparent-concurrency, in respect to the implementations.
Contents
Problem
Not everything should be required to be implemented thread-safe. See comments from John Ousterhout regarding multi-threading. Encapsulation of thread-affinity should be easy.
Solution
The Uno Threading Framework basically is going to introduce the notion of an apartment into the Uno world. An apartment in Uno terms is a purpose environment. Such an environment can be seen as a dedicated part of a process, giving space for objects of the same Object Binary Interface (OBI) and the same purpose. An environment can only be entered and left via defined doors, being proxy objects representing objects outside respectively inside the environment.
All calls from one Uno Environment to another are intercepted, references to local objects are replaced with proxies to these local objects, this operation is called "mapping" in UNO terms. Actually, an object gets "mapped" from one Uno Environment to another. Proxies already representing to be mapped objects of another Uno Environment become reused during the "mapping" operation, ensuring that an object can only be "mapped" once.
Purpose environments may be dedicated to MutExes or threads. In the sense, that a MutEx becomes acquired or a thread gets switched before a call enters an environment.
Time Frame
Current understanding of the topic lets us think, that the first changes of OOo / Uno on behalf of the Threading Framework are going to be integrated into one of the next updates, probably mid in 2006. The plan is, to implement the whole stack into the UTF2 CWS to ensure that everything works as expected, and to split the implementation into 'integration chunks', to be integrated with different CWS, to reduce the risk of breaking anything.
Tasks
| Area | Title | State | Location |
| Binary Uno | Implement Threading-Model | 90% | UTF2 |
| Binary Uno | Adapt Threading Architecture | 90% | UTF2 |
| Binary Uno | Uno/Effort/Binary/Implement Environment Stack Support | 50% | UTF2 |
| Binary Uno | Purpose Bridge Tester | 80% | UTF2 |
| C++ Uno | Threading-Model | 75% | UTF2 |
| C++ Uno | Misc Improvements | 100% | UTF2 |
| C++ Uno | Purpose Bridge Implementation Helper | 100% | UTF2 |
