The active object design pattern decouples method execution from method invocation for objects that each reside in their own thread of control. Typically, an active object is constructed using an internal thread and a queue of operations or events that will be executed on the active object’s thread. The goal is to enable concurrency using asynchronous invocation, and to eliminate the need for an object to worry about managing threading details itself: that’s all taken care of under the hood.
From Around the Web
- What is an Active Object? by Matthew Eshleman
- Active Objects (Actors) by Miro Samek
- Programming embedded systems: active objects in real-time by Miro Samek
- Beyond the RTOS by Miro Samek
- Programming embedded systems: event-driven active objects by Miro Samek
- Quantum Programming for Embedded Systems: Toward a Hassle-Free Multithreading by Miro Samek
- Managing Concurrency in Complex Embedded Systems by Dr. David M. Cummings
- Prefer Using Active Objects Instead of Naked Threads by Herb Sutter
- Know When to Use an Active Object Instead of a Mutex by Herb Sutter
- Message Passing for Intertask Communication by Dr. David Kalinsky
- New Directions in RTOS Kernels by Dr. David Kalinsky
- The Actor Model: Towards Better Concurrency by Dror Bereznitsky
- Active Object by Rainer Grimm
Synonyms:
Actor
Categories: Field Atlas
« Back to Glossary Index
Looks like the link for “Know When to Use Active Objects Instead of a Mutex” is broken. The new link is: https://www.state-machine.com/doc/Sutter2010b.pdf
Thanks, updated!