Proactor pattern

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
gollark: In a proprietary binary format also used for the potatOS Registry.
gollark: PotatOS with extended monitoring turned on logs every event but timers.
gollark: It's actually the potatOS logs storage.
gollark: How do you have my head?!
gollark: I hope it is investigatized investigazotobly.

See also
  • Reactor pattern (a pattern that also asynchronously queues events, but demultiplexes and dispatches them synchronously)

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


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.