Difference between revisions of "Uno/Term/Thread Affine"
From Apache OpenOffice Wiki
m (Uno/Spec/Thread Affine moved to Uno/Term/Thread Affine: It is not a specification, but a term.) |
m (Added category.) |
||
| Line 2: | Line 2: | ||
: Thread affine code must not care of any threading issues, ''including'' thread affinity. Thread affine code must be implemented [[Thread Transparent]]. On the designed level of granularity methods are guaranteed to not be called concurrelty. Thread calling thread ''does not'' vary over time. | : Thread affine code must not care of any threading issues, ''including'' thread affinity. Thread affine code must be implemented [[Thread Transparent]]. On the designed level of granularity methods are guaranteed to not be called concurrelty. Thread calling thread ''does not'' vary over time. | ||
: Declaring code to be thread affine is e.g. very usable for programming Windows thread affine APIs as OLE or WIN32. | : Declaring code to be thread affine is e.g. very usable for programming Windows thread affine APIs as OLE or WIN32. | ||
| + | |||
| + | [[Category:Uno:Term]] | ||
Revision as of 15:51, 15 May 2006
- The Thread Affine Code
- Thread affine code must not care of any threading issues, including thread affinity. Thread affine code must be implemented Thread Transparent. On the designed level of granularity methods are guaranteed to not be called concurrelty. Thread calling thread does not vary over time.
- Declaring code to be thread affine is e.g. very usable for programming Windows thread affine APIs as OLE or WIN32.
