Difference between revisions of "Uno/Effort/Binary/Extend Threading-Model"

From Apache OpenOffice Wiki
< Uno
Jump to: navigation, search
m (→‎Time Frame)
m (Fixed path to cppuhelper/tests/loader.)
 
(68 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
==Creating the UNO Threading Framework==
+
Type: [[Uno/Term/Effort|effort]]  Status: Finished  Owner: [[KR|Kay Ramme]]  Availability: URE 1.3 (SRC680_m212)
  
−
[mailto:Kay.Ramme@sun.com], [mailto:Kai.Sommerfeld@sun.com]
+
'''The mission of this effort is, to extend the [[Uno]] threading-model, to provide a way to design an applications [[Uno/Term/Threading-Architecture|threading-architecture]] independent of the implementations.''' This can be described as [[Uno/Term/Transparent Concurrency|'''transparent-concurrency''']] wrt the implementations.
  
−
Status: in progress
+
==Problem==
 +
Not everything should be required to be implemented [[Uno/Term/Thread Safe|thread-safe]]. E.g. see [http://home.pacbell.net/ouster/threads.pdf comments] from John Ousterhout regarding multi-threading. Encapsulation of [[Uno/Term/Thread Affine|thread-affinity]] should be easy.
  
−
===Purpose===
+
==Solution==
 +
The extended [[Uno]] threading-model is basically going to introduce the notion of an apartment into the [[Uno]] world. An apartment in [[Uno/Term|Uno terms]] is a [[Uno/Spec/Purpose Environment|purpose environment]]. Such an environment can be seen as a dedicated part of a process, giving space for objects of the same [[Uno/Term/Object Binary Interface|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.
  
−
'''The goal of the UNO threading framrwork 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.
+
[[Image:UNO_Envs.jpg]]
  
−
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 [[../../Spec/Purpose Environment | Purpose Environment]]. Such an environment can be seen as a dedicated part of a process, giving space for objects of the same ABI 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/Spec/Environment|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/Spec/Environment|Uno Environment]] to another. Proxies already representing to be mapped objects of another [[Uno/Spec/Environment|Uno Environment]] become reused during the "mapping" operation, ensuring that an object can only be "mapped" once.
  
−
[[Image:UNO_Envs.jpg]]
+
[[Uno/Spec/Purpose Environment|Purpose environments]] may be dedicated to MutExes or [[Wikipedia:Thread_%28computer_science%29|threads]]. In the sense, that a MutEx becomes acquired or a [[Wikipedia:Thread_%28computer_science%29|thread]] gets switched to before a call enters an environment.
  
−
All calls from one [[Uno/Spec/Environment | 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/Spec/Environment | UNO Environment]] to another. Proxies already representing to be mapped objects of another [[Uno/Spec/Environment | UNO Environment]] become reused during the "mapping" operation, ensuring that an object can only be "mapped" once.
+
==Time Frame==
 +
Understanding of the topic let us think, that the first changes of OOo / [[Uno]] on behalf of the extended [[Uno/Term/Threading-Model|threading-model]] were going to be integrated into one of the updates in 2006. The plan was, to implement the whole stack into the {{Uno/CWS|SRC680|utf2}} [[CWS]], which had been done, to ensure that everything worked as expected. The implementation has finally be done in the {{Uno/CWS|SRC680|bunoexttm}} [[CWS]] and is currently in QA. Expectation is, that the extended [[Uno/Binary|Binary Uno]] threading model is going to be available with OOo 2.3.
  
−
[[../../Spec/Purpose Environment|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.
+
==Tasks==
 +
{|border="1" cellspacing="0" class="wikitable"
 +
|- style="background:#efefef;"
 +
! Area !! Title !! State !! [[CWS]]
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Spec/Threading-Model|Specify Threading-Model]] ||  style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Spec/Environment Stack|Specify Environment Stack]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Impl/Environment Stack|Implement Environment Stack]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Test/Environment Stack|Implement Test for Environment Stack]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Spec/Cascaded Mapping|Specify Cascaded Mapping]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Impl/Cascaded Mapping|Implement Cascaded Mapping]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Test/Cascaded Mapping|Implement Test for Cascaded Mapping]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Spec/Environment Descriptor|Specify Environment Descriptor]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Impl/Environment Descriptor|Implement Environment Descriptor]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Test/Environment Descriptor|Implement Test for Environment Descriptor]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Spec/Environment Substitution|Specify Environment Substitution]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Impl/Environment Substitution|Implement Environment Substitution]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Test/Environment Substitution|Implement Test for Environment Substitution]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Spec/Thread Unsafety Bridge|Specify Thread Unsafety Bridge]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Impl/Thread Unsafety Bridge|Implement Thread Unsafety Bridge]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Test/Thread Unsafety Bridge|Implement Test for Thread Unsafety Bridge]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Spec/Thread Affinity Bridge|Specify Thread Affinity Bridge]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Impl/Thread Affinity Bridge|Implement Thread Affinity Bridge]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Binary|Binary Uno]] || [[Uno/Binary/Test/Thread Affinity Bridge|Implement Test for Thread Affinity Bridge]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
  
−
=== Background ===
+
| [[Uno/Binary|Binary Uno]] || Adapt Component Loader to support Purpose Environments || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
−
Code may actually vary in its capabilities regarding 'Transparent Concurrency'. Code may be differentiated into Code using
+
|-
−
* global variables, or
+
| [[Uno/Binary|Binary Uno]] || [[Uno/Cpp/Modules/CPPUhelper/tests/Loader|Test for Component Loaders support of Purpose Environments]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
−
* thread local variables, or
+
|-
−
* parameters only, or
+
| [[Uno/Binary|Binary Uno]] || Add support for extend getImplEnv function || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
−
* value parameters only, or
+
|-
−
* doing internal protection of critical sections, or
+
−
* not doing internal protection.
+
−
Such categorizations help to decide, what one can do with a particular implemention. Also the codes threading type is a compile time information and may therefor be used during compilation, so that the compiler may give errors when mixing thread safe and thread unsafe code in a multi thread scenario.
+
  
−
=== Time Frame ===
+
| [[Uno/Binary|Binary Uno]] || Adapt currentContext retrieval to support Purpose Environments || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
−
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 ===
+
| [[Uno/Cpp|C++ Uno]] || Adapt bootstrapping components || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
−
:{|border="1" cellspacing="0" class="wikitable"
+
−
|- style="background:#efefef;"  
+
−
| Title || Content || State
+
 
|-
 
|-
−
| Extend Binary UNO Threading Model ||
+
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Test/Bootstrap|Test for bootstrapping]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
−
* [[Uno/Effort/Binary/Thread Affinity Bridge|Binary UNO Thread Affinity Bridge]]
+
−
* [[Uno/Effort/Binary/Thread Unsafety Bridge|Binary UNO Thread Unsafety Bridge]]
+
−
* [[Uno/Effort/Binary/Purpose Environment|Binary UNO Purpose Environment]]
+
−
* [[Uno/Effort/Binary/Environment Stack|Binary UNO Environment Stack]]
+
−
* [[Uno/Effort/Binary/Cascaded Mapping|Binary UNO Cascaded Mapping]]
+
−
* [[Uno/Effort/Binary/Environment Substitution|Binary UNO Environment Substitution]]
+
−
|| open
+
 
|-
 
|-
−
| Extend C++ UNO Threading Model ||
+
 
−
* [[Uno/Effort/Cpp/Purpose Environment| C++ UNO Purpose Environment]]
+
| [[Uno/Cpp|C++ Uno]] || Add Purpose Environment to C++ bridges || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
−
* [[Uno/Effort/Cpp/Environment Stack|C++ UNO Environment Stack]]
+
−
|| open
+
 
|-
 
|-
−
| [[Uno/Effort/Binary/New Threading Architecture | New UNO Threading Architecture]] ||  || open
 
−
|}
 
  
−
=== Dependencies ===
+
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Spec/Threading-Model|Specify Threading-Model]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
−
:{|border="1" cellspacing="0" class="wikitable"
+
−
|- style="background:#efefef;"  
+
−
| Area || Effort || State
+
 
|-
 
|-
−
| [[Uno]] || Threading Model [[Uno/Spec/Threading Model|Specification]] || 90%
+
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Spec/Environment Stack|Specify Environment Stack]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 
|-
 
|-
−
| [[Uno/Binary | Binary Uno]] || [[Uno/Effort/Binary/Threading Model| the Threading Model]] || 90%
+
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Impl/Environment Stack|Implement Environment Stack]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 
|-
 
|-
−
| [[Uno/Binary | Binary Uno]] || [[Uno/Effort/Binary/Debug Bridge | Debugging Bridge]] || 90%
+
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Test/Environment Stack|Implement Test for Environment Stack]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 
|-
 
|-
−
| [[Uno/Cpp | C++ Uno]] || [[Uno/Effort/Cpp/Threading Model| the Threading Model]] || 75%
+
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Spec/Map Helpers|Specify Map Helpers]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 
|-
 
|-
−
| [[Uno/Java | Java Uno]] || [[Uno/Effort/Java/Threading Model | the Threading Model]] || 0%
+
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Impl/Map Helpers|Implement Map Helpers]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 
|-
 
|-
−
| [[Uno/CLI | CLI Uno]] || [[Uno/Effort/CLI/Threading Model|Uno Threading Model]] || 0%
+
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Test/Map Helpers|Implement Test for Map Helpers]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 
|-
 
|-
−
| [[Uno/Remote | Remote Uno]] || [[Uno/Effort/Remote/Threading Model|Uno Threading Model]] || 0%
+
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Spec/Shield Helpers|Specify Shield Helpers]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 
|-
 
|-
−
| [[Uno/Cpp | C++ Uno]] || [[Uno/Effort/Cpp/Misc | Misc Improvements]] || UTF2
+
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Impl/Shield Helpers|Implement Shield Helpers]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 
|-
 
|-
−
| [[Uno/Cpp | C++ Uno]] || [[Uno/Effort/Cpp/Purpose Bridge Implementation Helper | Purpose Bridge Implementation Helper]] || UTF2
+
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Test/Shield Helpers|Implement Test for Shield Helpers]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 
|-
 
|-
−
| [[Uno/Binary | Binary Uno]] || [[Uno/Binary/Jni-Uno Bridge | Jni-Uno Bridge]] - [[Uno/Spec/Purpose Environment | Purpose Environment]] Support || 0%
+
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Spec/FreeReference|Specify FreeReference]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Impl/FreeReference|Implement FreeReference]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Test/FreeReference|Implement Test for FreeReference]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Spec/Environment Guard|Specify Environment Guard]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Impl/Environment Guard|Implement Environment Guard]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Test/Environment Guard|Implement Test for Environment Guard]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Spec/Environment Descriptor|Specify Environment Descriptor]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Impl/Environment Descriptor|Implement Environment Descriptor]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Test/Environment Descriptor|Implement Test for Environment Descriptor]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Spec/Environment AntiGuard|Specify Environment AntiGuard]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Impl/Environment AntiGuard|Implement Environment AntiGuard]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Test/Environment AntiGuard|Implement Test for Environment AntiGuard]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Spec/Purpose Bridge Implementation Helper|Specify Purpose Bridge Implementation Helper]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Impl/Purpose Bridge Implementation Helper|Implement Purpose Bridge Implementation Helper]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|-
 +
| [[Uno/Cpp|C++ Uno]] || [[Uno/Cpp/Test/Purpose Bridge Implementation Helper|Test for Purpose Bridge Implementation Helper]] || style="background:lightgreen;" | 100% || {{Uno/CWS|SRC680|bunoexttm}}
 +
|}
 +
 
 +
==Dependencies==
 +
{|border="1" cellspacing="0" class="wikitable"
 +
|- style="background:#efefef;"
 +
! Area !! Title !! State !! [[CWS]]
 
|-
 
|-
−
| [[Uno/Binary | Binary Uno]] || [[Uno/Effort/Binary/ABI Bridge Tester | ABI Bridge Tester]] || 0%
+
| [[Uno/Cpp|C++ Uno]] ||  
 +
Misc Improvements
 +
* [[Uno/Cpp/Spec/Environment|uno::Environment]] Convenience Constructors
 +
* [[Uno/Cpp/Spec/Mapping|uno::Mapping]] Convenience Constructors
 +
|| 100% || {{Uno/CWS|SRC680|krmisc}} (SRC680_m191)
 
|-
 
|-
−
| [[Uno/Binary | Binary Uno]] || [[Uno/Effort/Binary/Purpose Bridge Tester | Purpose Bridge Tester]] || 0%
+
| [[Uno/Binary|Binary Uno]] ||  
 +
Preparation
 +
* enable identity mapping: getting a Uno Mapping from and to the same environment - currently the runtime does return NULL, so every client has to check for it,
 +
* cleanup the dll component loader
 +
** to use the identity mapping, and
 +
** to get rid of very outdated deprecated stuff
 +
|| 100% || {{Uno/CWS|SRC680|bunoidmap}} (SRC680_m196)
 
|-
 
|-
−
| [[Uno/Java | Java Uno]] || [[Uno/Java/Java-Urp Bridge | Java-Urp Bridge]] - [[Uno/Spec/Purpose Environment | Purpose Environment]] Support || 0%
+
| [[Uno/Binary|Binary Uno]] || [[Uno/Effort/Binary/Implement Environment Tester|Implement Environment Tester]] || 100% || {{Uno/CWS|SRC680|bunoexttm}}
 
|-
 
|-
−
| [[Uno/Binary | Binary Uno]] || [[Uno/Effort/Binary/Component Loader/Purpose Environment Support | Purpose Environment Support for the Component Loader]] || 0%
+
| [[Uno/Binary|Binary Uno]] || [[Uno/Effort/Binary/Implement Mapping Tester|Implement Mapping Tester]] || 100% || {{Uno/CWS|SRC680|bunoexttm}}
 
|-
 
|-
−
| [[Uno/Binary | Binary Uno]] || [[Uno/Binary/Uno-Urp Bridge | Uno-Urp Bridge]] - [[Uno/Spec/Purpose Environment | Purpose Environment]] Support || 0%
 
 
|}
 
|}
  
  
−
[[Category:Uno:Effort]]
+
[[Category:Effort]]
 +
[[Category:Uno]]
 +
[[Category:Uno:Binary]]
 +
[[Category:Multi-Threading]]

Latest revision as of 12:40, 20 October 2009

Type: effort Status: Finished Owner: Kay Ramme Availability: URE 1.3 (SRC680_m212)

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.

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.

UNO Envs.jpg

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

Understanding of the topic let us think, that the first changes of OOo / Uno on behalf of the extended threading-model were going to be integrated into one of the updates in 2006. The plan was, to implement the whole stack into the utf2 CWS, which had been done, to ensure that everything worked as expected. The implementation has finally be done in the bunoexttm CWS and is currently in QA. Expectation is, that the extended Binary Uno threading model is going to be available with OOo 2.3.

Tasks

Area Title State CWS
Binary Uno Specify Threading-Model 100% bunoexttm
Binary Uno Specify Environment Stack 100% bunoexttm
Binary Uno Implement Environment Stack 100% bunoexttm
Binary Uno Implement Test for Environment Stack 100% bunoexttm
Binary Uno Specify Cascaded Mapping 100% bunoexttm
Binary Uno Implement Cascaded Mapping 100% bunoexttm
Binary Uno Implement Test for Cascaded Mapping 100% bunoexttm
Binary Uno Specify Environment Descriptor 100% bunoexttm
Binary Uno Implement Environment Descriptor 100% bunoexttm
Binary Uno Implement Test for Environment Descriptor 100% bunoexttm
Binary Uno Specify Environment Substitution 100% bunoexttm
Binary Uno Implement Environment Substitution 100% bunoexttm
Binary Uno Implement Test for Environment Substitution 100% bunoexttm
Binary Uno Specify Thread Unsafety Bridge 100% bunoexttm
Binary Uno Implement Thread Unsafety Bridge 100% bunoexttm
Binary Uno Implement Test for Thread Unsafety Bridge 100% bunoexttm
Binary Uno Specify Thread Affinity Bridge 100% bunoexttm
Binary Uno Implement Thread Affinity Bridge 100% bunoexttm
Binary Uno Implement Test for Thread Affinity Bridge 100% bunoexttm
Binary Uno Adapt Component Loader to support Purpose Environments 100% bunoexttm
Binary Uno Test for Component Loaders support of Purpose Environments 100% bunoexttm
Binary Uno Add support for extend getImplEnv function 100% bunoexttm
Binary Uno Adapt currentContext retrieval to support Purpose Environments 100% bunoexttm
C++ Uno Adapt bootstrapping components 100% bunoexttm
C++ Uno Test for bootstrapping 100% bunoexttm
C++ Uno Add Purpose Environment to C++ bridges 100% bunoexttm
C++ Uno Specify Threading-Model 100% bunoexttm
C++ Uno Specify Environment Stack 100% bunoexttm
C++ Uno Implement Environment Stack 100% bunoexttm
C++ Uno Implement Test for Environment Stack 100% bunoexttm
C++ Uno Specify Map Helpers 100% bunoexttm
C++ Uno Implement Map Helpers 100% bunoexttm
C++ Uno Implement Test for Map Helpers 100% bunoexttm
C++ Uno Specify Shield Helpers 100% bunoexttm
C++ Uno Implement Shield Helpers 100% bunoexttm
C++ Uno Implement Test for Shield Helpers 100% bunoexttm
C++ Uno Specify FreeReference 100% bunoexttm
C++ Uno Implement FreeReference 100% bunoexttm
C++ Uno Implement Test for FreeReference 100% bunoexttm
C++ Uno Specify Environment Guard 100% bunoexttm
C++ Uno Implement Environment Guard 100% bunoexttm
C++ Uno Implement Test for Environment Guard 100% bunoexttm
C++ Uno Specify Environment Descriptor 100% bunoexttm
C++ Uno Implement Environment Descriptor 100% bunoexttm
C++ Uno Implement Test for Environment Descriptor 100% bunoexttm
C++ Uno Specify Environment AntiGuard 100% bunoexttm
C++ Uno Implement Environment AntiGuard 100% bunoexttm
C++ Uno Implement Test for Environment AntiGuard 100% bunoexttm
C++ Uno Specify Purpose Bridge Implementation Helper 100% bunoexttm
C++ Uno Implement Purpose Bridge Implementation Helper 100% bunoexttm
C++ Uno Test for Purpose Bridge Implementation Helper 100% bunoexttm

Dependencies

Area Title State CWS
C++ Uno

Misc Improvements

100% krmisc (SRC680_m191)
Binary Uno

Preparation

  • enable identity mapping: getting a Uno Mapping from and to the same environment - currently the runtime does return NULL, so every client has to check for it,
  • cleanup the dll component loader
    • to use the identity mapping, and
    • to get rid of very outdated deprecated stuff
100% bunoidmap (SRC680_m196)
Binary Uno Implement Environment Tester 100% bunoexttm
Binary Uno Implement Mapping Tester 100% bunoexttm
Retrieved from "https://wiki.openoffice.org/w/index.php?title=Uno/Effort/Binary/Extend_Threading-Model&oldid=143602"
Personal tools