Jump to content

Proactor pattern

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Ipsign (talk | contribs) at 04:53, 26 October 2010 (External links: added intra-wiki link). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Proactor is a software design pattern for Event handling in which long running activities are running in an asynchronous part. A Completion Handler is called after the asynchronous part has terminated. The proactor pattern can be considered to be an asynchronous variant of the synchronous reactor pattern[1].

Interaction

UML Sequence diagram of Proactor

Operation specific actors:

  • The Proactive Initiator starts the asynchronous operation via the Asynchronous Operation Processor and defines the Completion Handler
  • Completion Handler is a call at the end of the operation from the Asynchronous Operation Processor
  • Asynchronous Operation

Standardized actors

  • The Asynchronous Operation Processor controls the whole asynchronous operation
  • The Completion Dispatcher handles the call , depending on the execution environment.

Implementations

References

  1. ^ Pattern-Oriented Software Architecture, Volume 2, Schmidt et al., Jon Wiley & Sons, Ltd, 2000