Difference between revisions of "Uno/Term/Thread Affine"
From Apache OpenOffice Wiki
m (Added link to Thread Affinity Bridge.) |
|||
| Line 1: | Line 1: | ||
| − | ; Thread Affine: Code is Thread Affine, if it offers services to particular threads only (e.g. on Win32 the DestroyWindow function may only be called with a hWnd created by the same thread). Thread affine code is [[Uno/Term/Thread Aware|thread aware]]. | + | ; Thread Affine: Code is Thread Affine, if it offers services to particular threads only (e.g. on Win32 the DestroyWindow function may only be called with a hWnd created by the same thread). Thread affine code is [[Uno/Term/Thread Aware|thread aware]]. |
| − | Thread affine objects may be encapsulated by the [[Uno/Spec/Thread Affinity Bridge|Thread Affinity Environment]], ensuring [[Uno/Term/Thread Transparent|thread transparency]]. | + | Thread affine objects may be encapsulated by the [[Uno/Spec/Thread Affinity Bridge|Thread Affinity Environment]], ensuring [[Uno/Term/Thread Transparent|thread transparency]]. Thus, with thread unsafe code, thread affine code shares the property that locking is dealt with by the purpose environment. |
| − | + | ||
[[Category:Uno:Term]] | [[Category:Uno:Term]] | ||
Revision as of 08:43, 28 July 2006
- Thread Affine
- Code is Thread Affine, if it offers services to particular threads only (e.g. on Win32 the DestroyWindow function may only be called with a hWnd created by the same thread). Thread affine code is thread aware.
Thread affine objects may be encapsulated by the Thread Affinity Environment, ensuring thread transparency. Thus, with thread unsafe code, thread affine code shares the property that locking is dealt with by the purpose environment.
