This article relies largely or entirely on a single source. Relevant discussion may be found on the talk page. Please help improve this articlebyintroducing citations to additional sources.
Find sources: "Proactor pattern" – news · newspapers · books · scholar · JSTOR (March 2024) |
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]
Operation specific actors:
Standardized actors
| |||||||
---|---|---|---|---|---|---|---|
Gang of Four patterns |
| ||||||
Concurrency patterns |
| ||||||
Architectural patterns |
| ||||||
Other patterns |
| ||||||
Books |
| ||||||
People |
| ||||||
Communities |
| ||||||
See also |
|
![]() | This software-engineering-related article is a stub. You can help Wikipedia by expanding it. |