Difference between revisions of "Uno/Effort/Binary/Extend Threading-Model"
m (→Tasks: Added cascaded mapping.) |
m (→Tasks: Added tests for Env. Substs and Cas. Mapping .) |
||
| Line 52: | Line 52: | ||
|- | |- | ||
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Impl/Environment Substitution|Implement Environment Substitution]] || 100% || {{Uno/CWS|SRC680|bunoexttm}} | | [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Impl/Environment Substitution|Implement Environment Substitution]] || 100% || {{Uno/CWS|SRC680|bunoexttm}} | ||
| + | |- | ||
| + | | [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Test/Environment Substitution|Implement Test for Environment Substitution]] || 100% || {{Uno/CWS|SRC680|bunoexttm}} | ||
|- | |- | ||
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Spec/Cascaded Mapping|Specify Cascaded Mapping]] || 100% || n/a | | [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Spec/Cascaded Mapping|Specify Cascaded Mapping]] || 100% || n/a | ||
|- | |- | ||
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Impl/Cascaded Mapping|Implement Cascaded Mapping]] || 100% || {{Uno/CWS|SRC680|bunoexttm}} | | [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Impl/Cascaded Mapping|Implement Cascaded Mapping]] || 100% || {{Uno/CWS|SRC680|bunoexttm}} | ||
| + | |- | ||
| + | | [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Test/Cascaded Mapping|Implement Test for Cascaded Mapping]] || 100% || {{Uno/CWS|SRC680|bunoexttm}} | ||
|- | |- | ||
| [[Uno/Binary|Binary Uno]] || [[Uno/Effort/Binary/Adapt Threading-Architecture|Adapt Threading Architecture]] || 90% || {{Uno/CWS|SRC680|utf2}} | | [[Uno/Binary|Binary Uno]] || [[Uno/Effort/Binary/Adapt Threading-Architecture|Adapt Threading Architecture]] || 90% || {{Uno/CWS|SRC680|utf2}} | ||
Revision as of 13:58, 9 February 2007
Type: effort Status: in progress Owner: Kay Ramme
The mission of this effort is, to extend the Uno threading-model, to provide a way to design an applications threading-architecture independent of the implementations. This can be described as transparent-concurrency wrt the implementations.
Contents
Problem
Not everything should be required to be implemented thread-safe. E.g. see comments from John Ousterhout regarding multi-threading. Encapsulation of thread-affinity should be easy.
Solution
The extended Uno threading-model is basically 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 to 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 extend threading-model are going to be integrated into one of the next updates, probably late 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.
