It is sad that CPA in Seneca doesn’t offer any course about Software Design Patterns.
I just read through chapter two about ‘Subject Observers Pattern’.
Subject Observers pattern is useful when a bunch of observer objects need to be notified about change in the subject object. Observers registers themselves to get notifications from the Subject. When there is a change in any data in Subject, the subject notifies all the observers about the change. The subject object maintains a list of all the observer objects. When an observer unregisters itself, it is removed from this list. So next time, the subject notifies all the observers in its list, the unregisters are not sent any more notifications.
For example, a weather tracking system that sends temperature information to all the clients every time the temperature changes.Reading ‘Head First Design Patterns’
June 3, 2010 by ·
It is sad that CPA in Seneca doesn’t offer any course about Software Design Patterns.
I just read through chapter two about ‘Subject Observers Pattern’.
Subject Observers pattern is useful when a bunch of observer objects need to be notified about change in the subject object. Observers registers themselves to get notifications from the Subject. When there is a change in any data in Subject, the subject notifies all the observers about the change. The subject object maintains a list of all the observer objects. When an observer unregisters itself, it is removed from this list. So next time, the subject notifies all the observers in its list, the unregisters are not sent any more notifications.
For example, a weather tracking system that sends temperature information to all the clients every time the temperature changes.