Transcription of Reactor - Brian Foote
{{id}} {{{paragraph}}}
Douglas C. Schmidt 1998, 1999, all rights reserved, Siemens AG 1998, 1999, all rights reservedReactorTheReactordesign pattern handles service requests that are deliv-ered concurrently to an application by one or more known asDispatcher, NotifierExampleConsider an event-driven server for a distributed logging service. Cli-ent applications use the logging service to record information abouttheir status in a distributed environment. This status informationcommonly includes error notifications, debugging traces, and perfor-mance diagnostics. Logging records are sent to a central logging serv-er, which can write the records to various output devices, such as aconsole, a printer, a file, or a network management communicate with the logging server using a connection-ori-ented protocol, such as TCP [Ste90]: clients and the logging serviceare bound to a connection endpoint designated by an IP address anda TCP port number on the clients and logging server.
Structure The key participants in the Reactor pattern include the following: Handles identify resources that are managed by an operating system. These resources commonly include, among others, network connec-tions, open files, timers, and synchronization objects.
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
{{id}} {{{paragraph}}}