Last week I'd played around with couple of design patterns in JavaScript (Constructor and Module pattern). I really liked the Module pattern i.e. the approach taken in JavaScript to enable encapsulation of data in a Class (functions in JavaScript). I was building an application using these Design patterns but found that making Ajax request inside a function in a module was not the right approach. JavaScript would send a request and start executing the next statement. I wanted to use an approach that would push the data from the Model whenever there was some new data available. This lead me to try the 'Observer pattern' in JavaScript.
After reading a bit on the Observer pattern, I realized that it's used in almost all client side JavaScript programs in the form of event handlers. All browser events are examples of this pattern i.e. whenever an event takes place, the registered event handler is fired. Here, you want a particular function to be executed whenever there is a change in the state of another object. The function can be viewed as an Observer which performs the necessary action when the state of another object - let's call it the 'Subject' changes. The 'Subject' is responsible for notifying the Observers of the change in state and pass the necessary data to it's Observers. To do this the Subject has to maintain a list of Observers who are interested in getting notifications.
In my application, I was trying to fetch tweets by sending an Ajax request to Twitter server. Once the tweets are available, I wanted all my observers to be notified with the recent tweets. Here, my Subject is 'Twitter' which is responsible for fetching the tweets and notifying all its observers whenever the data is available. Also, it is responsible for maintaining a list of observers who are interested in receiving notifications. The way I modeled this application is to define a generic class 'Subject' and a class 'Twitter' which would extend the Subject class.
Here the Subject class defines an array 'observerList' and two methods 'addObserver' and 'notifyObserver'. The addObserver method would add the observer object to the array and notifyObserver would iterate through the list of observers and send notifications whenever there is a new message. Now the Twitter class can extend the Subject class:
The constructor of Twitter class would call the parent constructor and then add the observer object (by invoking addObserver) to the list. Now it's ready to fetch the tweets for the provided handlerName. The init function then sends an Ajax request to fetch the tweets and once the data is received it would call the notifyObserver function. Note that the notifyObserver function is defined in the Subject class. The implementation of the Observer is pretty simple:
The Observer needs to provide the function (or the handler) that should be called when the Subject has a new message. In this case the updateFn would log the messages that it receives from the Subject.
After reading a bit on the Observer pattern, I realized that it's used in almost all client side JavaScript programs in the form of event handlers. All browser events are examples of this pattern i.e. whenever an event takes place, the registered event handler is fired. Here, you want a particular function to be executed whenever there is a change in the state of another object. The function can be viewed as an Observer which performs the necessary action when the state of another object - let's call it the 'Subject' changes. The 'Subject' is responsible for notifying the Observers of the change in state and pass the necessary data to it's Observers. To do this the Subject has to maintain a list of Observers who are interested in getting notifications.
In my application, I was trying to fetch tweets by sending an Ajax request to Twitter server. Once the tweets are available, I wanted all my observers to be notified with the recent tweets. Here, my Subject is 'Twitter' which is responsible for fetching the tweets and notifying all its observers whenever the data is available. Also, it is responsible for maintaining a list of observers who are interested in receiving notifications. The way I modeled this application is to define a generic class 'Subject' and a class 'Twitter' which would extend the Subject class.
Here the Subject class defines an array 'observerList' and two methods 'addObserver' and 'notifyObserver'. The addObserver method would add the observer object to the array and notifyObserver would iterate through the list of observers and send notifications whenever there is a new message. Now the Twitter class can extend the Subject class:
The constructor of Twitter class would call the parent constructor and then add the observer object (by invoking addObserver) to the list. Now it's ready to fetch the tweets for the provided handlerName. The init function then sends an Ajax request to fetch the tweets and once the data is received it would call the notifyObserver function. Note that the notifyObserver function is defined in the Subject class. The implementation of the Observer is pretty simple:
The Observer needs to provide the function (or the handler) that should be called when the Subject has a new message. In this case the updateFn would log the messages that it receives from the Subject.
Comments
Post a Comment