---
title: proactor pattern
slug: proactor-pattern
qid: Q142948
snapshot: proactor-pattern-017204-1c0ed2a530eb9777
content_hash: 1c0ed2a530eb9777166f9baa5e3c3752b8c01445cb8b26862f3124c27d3985a7
license: CC BY-SA 4.0
source: https://en.wikipedia.org/w/index.php?oldid=1375194890
tags: [116690198, 20340897, 23118434, 23468805, 23603337, 24043274, 27695885, 43348164]
---

# proactor pattern

> [!note] Provenance
> Snapshot `proactor-pattern-017204-1c0ed2a530eb9777` · content root `1c0ed2a530eb9777…`
> Derived from <https://en.wikipedia.org/w/index.php?oldid=1375194890> · Licensed CC BY-SA 4.0

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.

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. ==Implementations== Proactor and Boost.Asio (C++) Adaptive Communication Environment (C++) RJR (Ruby) ==See also== Reactor pattern (a pattern that also asynchronously queues events, but demultiplexes and dispatches them synchronously) ==References==
