Active Object Pattern

Decouples method execution from method invocation. The goal is to introduce concurrency, by using asynchronous method invocation and a scheduler for handling requests.

The pattern consists of six elements:

  1. A proxy, which provides an interface that allows clients to invoke publicly accessible methods on an active object
  2. An interface which defines an interface for executing the methods of an active object;
  3. An activation list, which maintains a buffer of pending method requests;
  4. A scheduler, which decides what method requests to execute next;
  5. A servant, which defines the behavior (implementation) and state modeled as an active object
  6. A future or callback, which allows the client to obtain the result of the method invocation.
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License