A subscriber is a component that receives notifications from a publisher and may request, ignore, or process newly available content independently. The publisher tracks subscribers and remains unaware of their implementations. section 12.1 section 12.1.1
A flexible subscriber arrangement lets components:
- Subscribe or unsubscribe without changing publisher code. section 12.1.1
- Choose whether and how to process each notification. section 12.1
- Maintain different responsibilities, such as logging events, accumulating a table, or displaying a graph. section 12.1 section 12.1.2
Figure 12.1 An example of the publisher–subscriber model. The publisher component produces hit events that are consumed as they occur by the subscriber components to generate the various reports.
Shows a publisher producing events consumed by multiple subscriber components. section 12.1


