- Defined in:
A synchronization point at which threads can pair and swap elements within pairs. Each thread presents some object on entry to the exchange method, matches with a partner thread, and receives its partner's object on return.
Thread-safe Variable Classes
Each of the thread-safe variable classes is designed to solve a different problem. In general:
- : Shared, mutable variable providing independent, uncoordinated, asynchronous change of individual values. Best used when the value will undergo frequent, complex updates. Suitable when the result of an update does not need to be known immediately.
- : Shared, mutable variable providing independent, uncoordinated, synchronous change of individual values. Best used when the value will undergo frequent reads but only occasional, though complex, updates. Suitable when the result of an update must be known immediately.
- : A simple object reference that can be updated atomically. Updates are synchronous but fast. Best used when updates a simple set operations. Not suitable when updates are complex. and are similar but optimized for the given data type.
- : Shared, stateless synchronization point. Used when two or more threads need to exchange data. The threads will pair then block on each other until the exchange is complete.
- : Shared synchronization point. Used when one thread must give a value to another, which must take the value. The threads will block on each other until the exchange is complete.
- : Shared, mutable, isolated variable which holds a different value for each thread which has access. Often used as an instance variable in objects which must maintain different state for different threads.
Exchanger. Beyond a handful of threads the performance will degrade rapidly due to contention on the single slot, but the algorithm will remain correct.
: Shared, mutable variables which provide
coordinated, synchronous, change of many stated. Used when multiple
value must change together, in an all-or-nothing transaction.
This implementation is very simple, using only a single slot for each
exchanger (unlike more advanced implementations which use an "arena").
This approach will work perfectly fine when there are only a few threads
accessing a single