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 synchronousreactor pattern.[1]
Reactor pattern (a pattern that also asynchronously queues events, but demultiplexes and dispatches them synchronously)
Referencesedit
^Pattern-Oriented Software Architecture, Volume 2, Schmidt et al., Jon Wiley & Sons, Ltd, 2000
External linksedit
Proactor - An Object Behavioral Pattern for Demultiplexing and Dispatching Handlers for Asynchronous Events, Irfan Pyarali, Tim Harrison, Douglas C. Schmidt, Thomas D. Jordan, 1997 (pdf 143 kB)
proactor, pattern, proactor, software, design, pattern, event, handling, which, long, running, activities, running, asynchronous, part, completion, handler, called, after, asynchronous, part, terminated, proactor, pattern, considered, asynchronous, variant, sy. 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 Contents 1 Interaction 2 Implementations 3 See also 4 References 5 External linksInteraction edit nbsp UML Sequence diagram of ProactorOperation 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 OperationStandardized actors The Asynchronous Operation Processor controls the whole asynchronous operation The Completion Dispatcher handles the call depending on the execution environment Implementations editProactor and Boost Asio C Adaptive Communication Environment C RJR Ruby See also editReactor pattern a pattern that also asynchronously queues events but demultiplexes and dispatches them synchronously References edit Pattern Oriented Software Architecture Volume 2 Schmidt et al Jon Wiley amp Sons Ltd 2000External links editProactor An Object Behavioral Pattern for Demultiplexing and Dispatching Handlers for Asynchronous Events Irfan Pyarali Tim Harrison Douglas C Schmidt Thomas D Jordan 1997 pdf 143 kB nbsp This software engineering related article is a stub You can help Wikipedia by expanding it vte Retrieved from https en wikipedia org w index php title Proactor pattern amp oldid 868447390, wikipedia, wiki, book, books, library,
