This articlerelies largely or entirely on asingle source. Relevant discussion may be found on thetalk page. Please helpimprove this article byintroducing citations to additional sources. Find sources: "Proactor pattern" – news ·newspapers ·books ·scholar ·JSTOR(March 2024)

Proactor is asoftware design pattern forevent handling in which long running activities are running in an asynchronous part. Acompletion handler is called after the asynchronous part has terminated. The proactor pattern can be considered to be anasynchronous variant of thesynchronousreactor pattern.^[1]

Operation specific actors:

• TheProactive 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

• TheAsynchronous Operation Processor controls the whole asynchronous operation
• TheCompletion Dispatcher handles the call, depending on the execution environment.

• Proactor and Boost.Asio (C++)
• Adaptive Communication Environment (C++)
• RJR (Ruby)

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

• 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)

Thissoftware-engineering-related article is astub. You can help Wikipedia byadding missing information.

• v
• t
• e

• Events (computing)
• Software design patterns
• Software engineering stubs

• Articles with short description
• Short description is different from Wikidata
• Articles needing additional references from March 2024
• All articles needing additional references
• All stub articles