Pattern-Oriented Software Architecture is a series of software engineering book describing software design patterns patterns languages. Architectural patterns. From Wikipedia, the free encyclopedia. This article is in list format, but may read better as prose. You can help by converting this article , if appropriate. Editing help is available.
|Published (Last):||27 April 2009|
|PDF File Size:||15.6 Mb|
|ePub File Size:||7.5 Mb|
|Price:||Free* [*Free Regsitration Required]|
The Boost. Asio library offers side-by-side support for synchronous and asynchronous operations. The advantages and disadvantages of this approach, when compared to a synchronous-only or Reactor approach, are outlined below. Let us examine how the Proactor design pattern is implemented in Boost.
Asio, without reference to platform-specific details. Proactor design pattern adapted from [POSA2]. Defines an operation that is executed asynchronously, such as an asynchronous read or write on a socket.
Executes asynchronous operations and queues events on a completion event queue when operations complete. Buffers completion events until they are dequeued by an asynchronous event demultiplexer.
Processes the result of an asynchronous operation. These are function objects, often created using boost :: bind. Blocks waiting for events to occur on the completion event queue, and returns a completed event to its caller. Calls the asynchronous event demultiplexer to dequeue events, and dispatches the completion handler i. Application-specific code that starts asynchronous operations. On many platforms, Boost.
Asio implements the Proactor design pattern in terms of a Reactor, such as select , epoll or kqueue. This implementation approach corresponds to the Proactor design pattern as follows:. A reactor implemented using select , epoll or kqueue.
When the reactor indicates that the resource is ready to perform the operation, the processor executes the asynchronous operation and enqueues the associated completion handler on the completion event queue. This is implemented by waiting on an event or condition variable until a completion handler is available in the completion event queue.
This is implemented by the operating system. Operations are initiated by calling an overlapped function such as AcceptEx. Called by Boost. Asio to dequeue events and their associated completion handlers.
However, if native support is not available, the library may also be implemented using synchronous event demultiplexors that typify the Reactor pattern, such as POSIX select. Long-duration operations are performed asynchronously by the implementation on behalf of the application. Consequently applications do not need to spawn many threads in order to increase concurrency. Implementation strategies such as thread-per-connection which a synchronous-only approach would require can degrade system performance, due to increased context switching, synchronisation and data movement among CPUs.
With asynchronous operations it is possible to avoid the cost of context switching by minimising the number of operating system threads — typically a limited resource — and only activating the logical threads of control that have events to process. Asynchronous operation completion handlers can be written as though they exist in a single-threaded environment, and so application logic can be developed with little or no concern for synchronisation issues.
Function composition refers to the implementation of functions to provide a higher-level operation, such as sending a message in a particular format. Each function is implemented in terms of multiple calls to lower-level read or write operations. For example, consider a protocol where each message consists of a fixed-length header followed by a variable length body, where the length of the body is specified in the header.
To compose functions in an asynchronous model, asynchronous operations can be chained together. That is, a completion handler for one operation can initiate the next. Starting the first call in the chain can be encapsulated so that the caller need not be aware that the higher-level operation is implemented as a chain of asynchronous operations.
The ability to compose new operations in this way simplifies the development of higher levels of abstraction above a networking library, such as functions to support a specific protocol. It is more difficult to develop applications using asynchronous mechanisms due to the separation in time and space between operation initiation and completion.
Applications may also be harder to debug due to the inverted flow of control. Buffer space must be committed for the duration of a read or write operation, which may continue indefinitely, and a separate buffer is required for each concurrent operation.
The Reactor pattern, on the other hand, does not require buffer space until a socket is ready for reading or writing. Wiley, Distributed under the Boost Software License, Version 1. This is the documentation for an old version of Boost. Click here to view this page for the latest version. A linked list of completion handlers i.
Reactor pattern (POSA2) explained