Summary
(Top)
| Concept | A system must respond to two or more events in an asynchronous manner. A container component is used to handle common technology details that would otherwise need to be handled by each event processor component. |
| Component Types | Container, event processors, and configuration documents. |
| Connector Types | Request/reply, document reading, component invokation. |
| Relations | The container holds the event processors, reads configuration documents, and invokes event processors as needed. |
| Computational Model | Clients initiate events by submitting a message stimulus to the container. The container uses configuration data to select and execute an appropriate event processor. The container invokes the selected processor which transforms the stimulus into a message response which the container formats and returns to the client. |
| Properties | Same as the client-server style. |
| Topology | The event processors and configuration documents are often enclosed in a boundary that represents the container. |
Relationship to Other Styles
(Top)
The container style is often the architecture used for a server component in a client-server architecture.
Prepared by David L. March -- Last Revised on April 9, 2003
COPYRIGHT © 2003 BY DAVID L. MARCH