Observer

Model–view–controller

Computer Science Design Patterns
Observer

Prototype

Scope

Object

Purpose

Behavioral

Intent

Define a one-to-many dependency between objects so that when one object changes state (the Subject), all its dependents (the Observers) are notified and updated automatically.

Applicability

when an abstraction has two aspects, one dependent on the other
when a change to one object requires changing others, and you don't know how many objects need to be changed
when an object should notify other objects without making assumptions about who these objects are

Structure

Consequences

+ modularity: subject and observers may vary independently
+ extensibility: can define and add any number of observers
+ customizability: different observers provide different views of subject
- unexpected updates: observers don't know about each other
- update overhead: might need hints

Implementation

subject-observer mapping
dangling references
avoiding observer-specific update protocols: the push and pull models
registering modifications of interest explicitly

Related pattern

Singleton, is used to make observable object unique and accessible globally.
Mediator, is used to encapsulate updated objects

Description

Problem: In one place or many places in the application we need to be aware about a system event or an application state change. We'd like to have a standard way of subscribing to listening for system events and a standard way of notifying the interested parties. The notification should be automated after an interested party subscribed to the system event or application state change. There should be a way to unsubscribe, too.

Forces: Observers and observables probably should be represented by objects. The observer objects will be notified by the observable objects.

Solution: After subscribing the listening objects will be notified by a way of method call.

Loose coupling: When two objects are loosely coupled, they can interact, but they have very little knowledge of each other. Strive for loosely coupled designs between objects that interact.

The only thing that Subject knows about an observer is that it implements a certain interface
We can add new observers at any time
We never need to modify the subject to add new types of observers
We can reuse subjects or observers independently of each other
Changes to either the subject or an observer will not affect the other

Examples

The Observer pattern is used extensively in Java. E.g. in the following piece of code

button is the Subject
MyListener is the Observer
actionPerformed() is the equivalent to update()

JButtonbutton=newJButton("Click me!");button.addActionListener(newMyListener());classMyListenerimplementsActionListener{publicvoidactionPerformed(ActionEventevent){...}}

Another example is the PropertyChangeSupport. The Component class uses a PropertyChangeSupport object to let interested observers register for notification of changes in the properties of labels, panels, and other GUI components.

Can you find the Subject, Observer and update() in the above class diagram?

Component is the Subject
PropertyChangeListener is the Observer
propertyChange() is the equivalent to update()

Cost

This pattern can be tricky if you do not beware. Beware the data representing the state changes of the subject can evolve without changing the interfaces. If you only transmit a string, the pattern could become very expensive if at least one new observer needs also a state code. You should use a mediator unless you know the implementation of the subject state will never change.

Creation

This pattern has a cost to create.

Maintenance

This pattern can be expensive to maintain.

Removal

This pattern has a cost to remove too.

Advises

Put the subject and observer term in the name of the subject and the observer classes to indicate the use of the pattern to the other developers.
To improve performances, you can only send to the observers the difference of states instead of the new state. The observers can only update following the changed part of the subject instead of all the state of the subject.

Implementations

Implementation in ActionScript 3

// Main Classpackage{importflash.display.MovieClip;publicclassMainextendsMovieClip{privatevar_cs:ConcreteSubject=newConcreteSubject();privatevar_co1:ConcreteObserver1=newConcreteObserver1();privatevar_co2:ConcreteObserver2=newConcreteObserver2();publicfunctionMain(){_cs.registerObserver(_co1);_cs.registerObserver(_co2);_cs.changeState(10);_cs.changeState(99);_cs.unRegisterObserver(_co1);_cs.changeState(17);_co1=null;}}}// Interface Subjectpackage{publicinterfaceISubject{functionregisterObserver(o:IObserver):void;functionunRegisterObserver(o:IObserver):void;functionupdateObservers():void;functionchangeState(newState:uint):void;}}// Interface Observerpackage{publicinterfaceIObserver{functionupdate(newState:uint):void;}}// Concrete Subjectpackage{publicclassConcreteSubjectimplementsISubject{privatevar_observersList:Array=newArray();privatevar_currentState:uint;publicfunctionConcreteSubject(){}publicfunctionregisterObserver(o:IObserver):void{_observersList.push(o);_observersList[_observersList.length-1].update(_currentState);// update newly registered}publicfunctionunRegisterObserver(o:IObserver):void{_observersList.splice(_observersList.indexOf(o),1);}publicfunctionupdateObservers():void{for(vari:uint=0;i<_observersList.length;i++){_observersList[i].update(_currentState);}}publicfunctionchangeState(newState:uint):void{_currentState=newState;updateObservers();}}}// Concrete Observer 1package{publicclassConcreteObserver1implementsIObserver{publicfunctionConcreteObserver1(){}publicfunctionupdate(newState:uint):void{trace("co1: "+newState);}// other Observer specific methods}}// Concrete Observer 2package{publicclassConcreteObserver2implementsIObserver{publicfunctionConcreteObserver2(){}publicfunctionupdate(newState:uint):void{trace("co2: "+newState);}// other Observer specific methods}}

Implementation in C#

Traditional Method

C# and the other .NET Framework languages do not typically require a full implementation of the Observer pattern using interfaces and concrete objects. Here is an example of using them, however.

usingSystem;usingSystem.Collections;namespaceWikipedia.Patterns.Observer{// IObserver --> interface for the observerpublicinterfaceIObserver{// called by the subject to update the observer of any change// The method parameters can be modified to fit certain criteriavoidUpdate(stringmessage);}publicclassSubject{// use array list implementation for collection of observersprivateArrayListobservers;// constructorpublicSubject(){observers=newArrayList();}publicvoidRegister(IObserverobserver){// if list does not contain observer, addif(!observers.Contains(observer)){observers.Add(observer);}}publicvoidUnregister(IObserverobserver){// if observer is in the list, removeobservers.Remove(observer);}publicvoidNotify(stringmessage){// call update method for every observerforeach(IObserverobserverinobservers){observer.Update(message);}}}// Observer1 --> Implements the IObserverpublicclassObserver1:IObserver{publicvoidUpdate(stringmessage){Console.WriteLine("Observer1:"+message);}}// Observer2 --> Implements the IObserverpublicclassObserver2:IObserver{publicvoidUpdate(stringmessage){Console.WriteLine("Observer2:"+message);}}// Test classpublicclassObserverTester{[STAThread]publicstaticvoidMain(){SubjectmySubject=newSubject();IObservermyObserver1=newObserver1();IObservermyObserver2=newObserver2();// register observersmySubject.Register(myObserver1);mySubject.Register(myObserver2);mySubject.Notify("message 1");mySubject.Notify("message 2");}}}

Using Events

The alternative to using concrete and abstract observers and publishers in C# and other .NET Framework languages, such as Visual Basic, is to use events. The event model is supported via delegates that define the method signature that should be used to capture events. Consequently, delegates provide the mediation otherwise provided by the abstract observer, the methods themselves provide the concrete observer, the concrete subject is the class defining the event, and the subject is the event system built into the base class library. It is the preferred method of accomplishing the Observer pattern in.NET applications.

usingSystem;// First, declare a delegate type that will be used to fire events.// This is the same delegate as System.EventHandler.// This delegate serves as the abstract observer.// It does not provide the implementation, but merely the contract.publicdelegatevoidEventHandler(objectsender,EventArgse);// Next, declare a published event. This serves as the concrete subject.// Note that the abstract subject is handled implicitly by the runtime.publicclassButton{// The EventHandler contract is part of the event declaration.publiceventEventHandlerClicked;// By convention,.NET events are fired from descendant classes by a virtual method,// allowing descendant classes to handle the event invocation without subscribing// to the event itself.protectedvirtualvoidOnClicked(EventArgse){if(Clicked!=null)Clicked(this,e);// implicitly calls all observers/subscribers}}// Then in an observing class, you are able to attach and detach from the events:publicclassWindow{privateButtonokButton;publicWindow(){okButton=newButton();// This is an attach function. Detaching is accomplished with -=.// Note that it is invalid to use the assignment operator - events are multicast// and can have multiple observers.okButton.Clicked+=newEventHandler(okButton_Clicked);}privatevoidokButton_Clicked(objectsender,EventArgse){// This method is called when Clicked(this, e) is called within the Button class// unless it has been detached.}}

Implementation in Java

Handy implementation

You can implement this pattern in Java like this:

// Observer pattern -- Structural example// @since JDK 5.0importjava.util.ArrayList;// "Subject"abstractclassSubject{// FieldsprivateArrayList<Observer>observers=newArrayList<Observer>();// Methodspublicvoidattach(Observerobserver){observers.add(observer);}publicvoiddetach(Observerobserver){observers.remove(observer);}publicvoidnotifyObservers(){for(Observero:observers)o.update();}}

// "ConcreteSubject"classConcreteSubjectextendsSubject{// FieldsprivateStringsubjectState;// PropertiespublicStringgetSubjectState(){returnsubjectState;}publicvoidsetSubjectState(Stringvalue){subjectState=value;}}

// "Observer"abstractclassObserver{// Methodsabstractpublicvoidupdate();}

// "ConcreteObserver"classConcreteObserverextendsObserver{// FieldsprivateStringname;privateStringobserverState;privateConcreteSubjectsubject;// ConstructorspublicConcreteObserver(ConcreteSubjectsubject,Stringname){this.subject=subject;this.name=name;//subject.attach(this);}// Methodspublicvoidupdate(){observerState=subject.getSubjectState();System.out.printf("Observer %s's new state is %s\n",name,observerState);}}

// Client testpublicclassClient{publicstaticvoidmain(String[]args){// Configure Observer structureConcreteSubjects=newConcreteSubject();s.attach(newConcreteObserver(s,"A"));s.attach(newConcreteObserver(s,"B"));s.attach(newConcreteObserver(s,"C"));// Change subject and notify observerss.setSubjectState("NEW");s.notifyObservers();}}

Built-in support

The Java JDK has several implementations of this pattern: application in Graphical User Interfaces such as in the AWT toolkit, Swing etc. In Swing, whenever a user clicks a button or adjusts a slider, many objects in the application may need to react to the change. Swing refers to interested clients (observers) as "listeners" and lets you register as many listeners as you like to be notified of a component's events.

MVC is more M(VC) in Swing, i.e. View and Controller are tightly coupled; Swing does not divide Views from Controllers. MVC supports n-tier development, i.e. loosely coupled layers (see below) that can change independently and that may even execute on different machines.

There is also a built-in support for the Observer pattern. All one has to do is extend java.util.Observable (the Subject) and tell it when to notify the java.util.Observer s. The API does the rest for you. You may use either push or pull style of updating your observers.

java.util.Observable is a class while java.util.Observer is an interface.

publicvoidsetValue(doublevalue){this.value=value;setChanged();notifyObservers();}

Note that you have to call setChanged() so that the Observable code will broadcast the change. The notifyObservers() method calls the update() method of each registered observer. The update() method is a requirement for implementers of the Observer Interface.

// Observer pattern -- Structural exampleimportjava.util.Observable;importjava.util.Observer;// "Subject"classConcreteSubjectextendsObservable{// FieldsprivateStringsubjectState;// MethodspublicvoiddataChanged(){setChanged();notifyObservers();// use the pull method}// PropertiespublicStringgetSubjectState(){returnsubjectState;}publicvoidsetSubjectState(Stringvalue){subjectState=value;dataChanged();}}

// "ConcreteObserver"importjava.util.Observable;importjava.util.Observer;classConcreteObserverimplementsObserver{// FieldsprivateStringname;privateStringobserverState;privateObservablesubject;// ConstructorspublicConcreteObserver(Observablesubject,Stringname){this.subject=subject;this.name=name;subject.addObserver(this);}// Methodspublicvoidupdate(Observablesubject,Objectarg){if(subjectinstanceofConcreteSubject){ConcreteSubjectsubj=(ConcreteSubject)subject;observerState=subj.getSubjectState();System.out.printf("Observer %s's new state is %s\n",name,observerState);}}}

// Client testpublicclassClient{publicstaticvoidmain(String[]args){// Configure Observer structureConcreteSubjects=newConcreteSubject();newConcreteObserver(s,"A");newConcreteObserver(s,"B");newConcreteObserver(s,"C");// Change subject and notify observerss.setSubjectState("NEW");}}

Keyboard handling

Below is an example written in Java that takes keyboard input and treats each input line as an event. The example is built upon the library classes java.util.Observer and java.util.Observable. When a string is supplied from System.in, the method notifyObservers is then called, in order to notify all observers of the event's occurrence, in the form of an invocation of their 'update' methods - in our example, ResponseHandler.update(...).

The file MyApp.java contains a main() method that might be used in order to run the code.

/* Filename : EventSource.java */packageorg.wikibooks.obs;importjava.util.Observable;// Observable is hereimportjava.io.BufferedReader;importjava.io.IOException;importjava.io.InputStreamReader;publicclassEventSourceextendsObservableimplementsRunnable{@Overridepublicvoidrun(){try{finalInputStreamReaderisr=newInputStreamReader(System.in);finalBufferedReaderbr=newBufferedReader(isr);while(true){Stringresponse=br.readLine();setChanged();notifyObservers(response);}}catch(IOExceptione){e.printStackTrace();}}}

/* Filename : ResponseHandler.java */packageorg.wikibooks.obs;importjava.util.Observable;importjava.util.Observer;/* this is Event Handler */publicclassResponseHandlerimplementsObserver{privateStringresp;publicvoidupdate(Observableobj,Objectarg){if(arginstanceofString){resp=(String)arg;System.out.println("\nReceived Response: "+resp);}}}

/* Filename : MyApp.java *//* This is the main program */packageorg.wikibooks.obs;publicclassMyApp{publicstaticvoidmain(String[]args){System.out.println("Enter Text >");// create an event source - reads from stdinfinalEventSourceeventSource=newEventSource();// create an observerfinalResponseHandlerresponseHandler=newResponseHandler();// subscribe the observer to the event sourceeventSource.addObserver(responseHandler);// starts the event threadThreadthread=newThread(eventSource);thread.start();}}

The Java implementation of the Observer pattern has pros and cons:

Pros

It hides many of the details of the Observer pattern
It can be used both pull and push ways.

Cons

Because Observable is a class, you have to subclass it; you can’t add on the Observable behavior to an existing class that subclasses another superclass (fails the programming to interfaces principle). If you can’t subclass Observable, then use delegation, i.e. provide your class with an Observable object and have your class forward key method calls to it.
Because setChanged() is protected, you can’t favour composition over inheritance.

Implementation in PHP

class STUDENT

<?phpclassStudentimplementsSplObserver{protected$type="Student";private$name;private$address;private$telephone;private$email;private$_classes=array();publicfunction__construct($name){$this->name=$name;}publicfunctionGET_type(){return$this->type;}publicfunctionGET_name(){return$this->name;}publicfunctionGET_email(){return$this->email;}publicfunctionGET_telephone(){return$this->telephone;}publicfunctionupdate(SplSubject$object){$object->SET_log("Comes from ".$this->name.": I'm a student of ".$object->GET_materia());}}?>

class TEACHER

<?phpclassTeacherimplementsSplObserver{protected$type="Teacher";private$name;private$address;private$telephone;private$email;private$_classes=array();publicfunction__construct($name){$this->name=$name;}publicfunctionGET_type(){return$this->type;}publicfunctionGET_name(){return$this->name;}publicfunctionGET_email(){return$this->email;}publicfunctionGET_telephone(){return$this->name;}publicfunctionupdate(SplSubject$object){$object->SET_log("Comes from ".$this->name.": I teach in ".$object->GET_materia());}}?>

Class SUBJECT

<?phpclassSubjectimplementsSplSubject{private$name_materia;private$_observers=array();private$_log=array();function__construct($name){$this->name_materia=$name;$this->_log[]="Subject $name was included";}/* Add an observer */publicfunctionattach(SplObserver$classes){$this->_classes[]=$classes;$this->_log[]=" The ".$classes->GET_type()." ".$classes->GET_name()." was included";}/* Remove an observer */publicfunctiondetach(SplObserver$classes){foreach($this->_classesas$key=>$obj){if($obj==$classes){unset($this->_classes[$key]);$this->_log[]=" The ".$classes->GET_type()." ".$classes->GET_name()." was removed";}}}/* Notificate an observer */publicfunctionnotify(){foreach($this->_classesas$classes){$classes->update($this);}}publicfunctionGET_materia(){return$this->name_materia;}functionSET_log($valor){$this->_log[]=$valor;}functionGET_log(){return$this->_log;}}?>

Application

<?phprequire_once("teacher.class.php");require_once("student.class.php");require_once("subject.class.php");$subject=newSubject("Math");$marcus=newTeacher("Marcus Brasizza");$rafael=newStudent("Rafael");$vinicius=newStudent("Vinicius");// Include observers in the math Subject$subject->attach($rafael);$subject->attach($vinicius);$subject->attach($marcus);$subject2=newSubject("English");$renato=newTeacher("Renato");$fabio=newStudent("Fabio");$tiago=newStudent("Tiago");// Include observers in the english Subject$subject2->attach($renato);$subject2->attach($vinicius);$subject2->attach($fabio);$subject2->attach($tiago);// Remove the instance "Rafael from subject"$subject->detach($rafael);// Notify both subjects$subject->notify();$subject2->notify();echo"First Subject <br>";echo"<pre>";print_r($subject->GET_log());echo"</pre>";echo"<hr>";echo"Second Subject <br>";echo"<pre>";print_r($subject2->GET_log());echo"</pre>";?>

OUTPUT

First Subject

Array ( [0] => Subject Math was included [1] => The Student Rafael was included [2] => The Student Vinicius was included [3] => The Teacher Marcus Brasizza was included [4] => The Student Rafael was removed [5] => Comes from Vinicius: I'm a student of Math [6] => Comes from Marcus Brasizza: I teach in Math )

Second Subject

Array ( [0] => Subject English was included [1] => The Teacher Renato was included [2] => The Student Vinicius was included [3] => The Student Fabio was included [4] => The Student Tiago was included [5] => Comes from Renato: I teach in English [6] => Comes from Vinicius: I'm a student of English [7] => Comes from Fabio: I'm a student of English [8] => Comes from Tiago: I'm a student of English )

Implementation in Python

The observer pattern in Python:

classAbstractSubject:defregister(self,listener):raiseNotImplementedError("Must subclass me")defunregister(self,listener):raiseNotImplementedError("Must subclass me")defnotify_listeners(self,event):raiseNotImplementedError("Must subclass me")classListener:def__init__(self,name,subject):self.name=namesubject.register(self)defnotify(self,event):printself.name,"received event",eventclassSubject(AbstractSubject):def__init__(self):self.listeners=[]self.data=NonedefgetUserAction(self):self.data=raw_input('Enter something to do:')returnself.data# Implement abstract Class AbstractSubjectdefregister(self,listener):self.listeners.append(listener)defunregister(self,listener):self.listeners.remove(listener)defnotify_listeners(self,event):forlistenerinself.listeners:listener.notify(event)if__name__=="__main__":# make a subject object to spy onsubject=Subject()# register two listeners to monitor it.listenerA=Listener("<listener A>",subject)listenerB=Listener("<listener B>",subject)# simulated eventsubject.notify_listeners("<event 1>")# outputs:# <listener A> received event <event 1># <listener B> received event <event 1>action=subject.getUserAction()subject.notify_listeners(action)#Enter something to do:hello# outputs:# <listener A> received event hello# <listener B> received event hello