Difference between revisions of "Uno/Spec/Thread Unsafety Bridge"
From Apache OpenOffice Wiki
m (→API: Typo.) |
(Removed implementation assumptions.) |
||
Line 5: | Line 5: | ||
=== Feature === | === Feature === | ||
− | This [[../Bridge|bridge]] protects [[Uno/Term/Thread Unsafe|thread unsafe]] objects from being called by multiple threads concurrently | + | This [[../Bridge|bridge]] protects [[Uno/Term/Thread Unsafe|thread unsafe]] objects from being called by multiple threads concurrently. |
− | + | Only one thread at a time can enter a Unsafety Environment, an Unsafety Environment is entered, if any thread has one of the methods provided by the <code>Enterable</code> API on the stack. | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
=== API === | === API === |
Revision as of 12:41, 28 June 2006
state: draft
type: specification
Thread Unsafety Bridge
Feature
This bridge protects thread unsafe objects from being called by multiple threads concurrently.
Only one thread at a time can enter a Unsafety Environment, an Unsafety Environment is entered, if any thread has one of the methods provided by the Enterable
API on the stack.
API
Purpose bridge named "unsafe"
.