Uno/Effort/Binary/Extend Threading-Model
Creating the UNO Threading Framework
Status: in progress
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.
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 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 apartment.
All calls from one environment to another are intercepted, references to local objects get replaced with proxies to these local objects, this operation is called "mapping" in UNO terms. An object gets "mapped" from one environment to another. Proxies already representing to be mapped objects of another 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.
The following specifications and features give an overview over the UNO Threading Framework. The specifications roughly depend on each other in the order listed. For example, the Threading Models specification depends on the Implementation Environments, all pieces basically creating a stack.
Tasks:
| Task | State |
| Specify the Uno Threading Model | 90% |
| Uno Threading Model for Binary UNO. | 90% |
| Debugging Bridge for Binary UNO. | 90% |
| Uno Threading Model for C++ UNO. | 75% |
| Uno Threading Model for Java UNO. | 0% |
| Uno Threading Model for CLI UNO. | 0% |
| Uno Threading Model for Remote UNO. | 0% |
| Cpp-Uno Bridge - Purpose Environment Support | UTF2 |
| C++ Misc Improvements | UTF2 |
| C++ Purpose Bridge Implementation Helper | UTF2 |
| Jni-Uno Bridge - Purpose Environment Support | 0% |
| Java-Urp Bridge - Purpose Environment Support | 0% |
| Purpose Environment Support for the Binary UNO Component Loader | 0% |
| Uno-Urp Bridge - Purpose Environment Support | 0% |
| New Binary UNO Testers | |||||||||
| Title | Spec | % | Changed | Impl | % | Changed | Test | % | Changed |
| Environment Stack Tester | draft | 80% | 01/27/2006 | UTF2 | 100% | 02/01/2006 | |||
| Mapping Tester | draft | 80% | 12/22/2005 | UTF2 | 100% | 01/30/2006 | |||
| Environment Tester | draft | 80% | 12/22/2005 | UTF2 | 100% | 02/17/2006 | |||
| Features for C++ UNO | |||||||||
| Title | Spec | % | Changed | Impl | % | Changed | Test | % | Changed |
| Test Helper: Object Factory | draft | 80% | 01/30/2006 | UTF2 | 100% | 01/31/2006 |
Current understanding of the topic lets us think, that the changes of OOo / UNO on behalf of the Threading Framework are going to be integrated into one of the next updates, probably early in 2006.
