Active Object [AO]

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

Related

Categories: Field Atlas Categories Field Atlas Tags Design Pattern, Multithreading, Public Entry

2 Replies to “Active Object [AO]”

patrick.wright says:

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

Phillip Johnston says: Thanks, updated!

Share Your ThoughtsCancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

The hard way is the fast way. Do it right the first time and you won't have to do it over the next time. James Clear
3-2-1: The Responsibility of Any Creator, Leadership and How to Succeed

Free Newsletter

Sign up and receive our free playbook for writing portable embedded software.

Featured Courses

©2024 Embedded Artistry LLC. All rights reserved.
EMBEDDED ARTISTRY and the OWL logo are registered trademarks of Embedded Artistry LLC.