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.
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.
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.
|Binary Uno||Implement Environment Tester||100%||bunoexttm|
|Binary Uno||Implement Mapping Tester||100%||bunoexttm|