Active Object
From Wikipedia, the free encyclopedia
As described by (Schmidt 00): The Active Object design pattern decouples method execution from method invocation that reside in their own thread of control.
The goal of an active object is to introduce concurrency, by using asynchronous method invocation and a scheduler for handling requests.
The active object pattern consists of six elements:
- a proxy, which provides an interface towards clients with publicly accessible methods
- an interface which defines the method request on an active object
- a list of pending requests from clients
- a scheduler, which decides which request to execute next
- the implementation of the active object method.
- a callback or variable for the client to receive the result.
[edit] References
- Bass, L., Clements, P., Kazman, R. Software Architecture in Practice. Addison Wesley, 2003
- D, Schmidt, M., Rohnert, H., Buschmann, F. (2000). Pattern-Oriented Software Architecture, Volume 2: Patterns for Concurrent and Networked Objects. John Wiley & Sons. ISBN 0-471-60695-2.