Difference between revisions of "Uno/Term/Thread Safe"
From Apache OpenOffice Wiki
m |
m (Added links to wikipedia.) |
||
| Line 1: | Line 1: | ||
| − | ; Thread Safe: Code is Thread Safe, if it can safely be called concurrently by multiple threads. This typically means, that it protects critical sections by locks. Thread Safe code is [[Uno/Term/Thread Aware|thread aware]]. | + | ; Thread Safe: Code is Thread Safe, if it can safely be called concurrently by multiple threads. This typically means, that it protects critical sections by locks. Thread Safe code is [[Uno/Term/Thread Aware|thread aware]]. [[Wikipedia:|Wikipedia]] has a more in-deep article about [[Wikipedia:Thread safety|thread safety]]. |
In UNO, components need to be declared Thread Safe, if doing blocking I/O, so that the components system calls can be interrupted. Thread safe components may also be used to allow high concurrency, while avoiding the runtime overhead of external locking. | In UNO, components need to be declared Thread Safe, if doing blocking I/O, so that the components system calls can be interrupted. Thread safe components may also be used to allow high concurrency, while avoiding the runtime overhead of external locking. | ||
[[Category:Uno:Term]] | [[Category:Uno:Term]] | ||
Revision as of 10:12, 27 July 2006
- Thread Safe
- Code is Thread Safe, if it can safely be called concurrently by multiple threads. This typically means, that it protects critical sections by locks. Thread Safe code is thread aware. Wikipedia has a more in-deep article about thread safety.
In UNO, components need to be declared Thread Safe, if doing blocking I/O, so that the components system calls can be interrupted. Thread safe components may also be used to allow high concurrency, while avoiding the runtime overhead of external locking.
