PureMVC::INotification Class Reference

The interface definition for a PureMVC Notification. More...

#include <pmvcpp.h>

Inheritance diagram for PureMVC::INotification:

Public Member Functions
virtual int	getName ()=0
	Get the name of the `INotification` instance.
virtual void	setBody (void *body)=0
	Set the body of the `INotification` instance.
virtual void *	getBody ()=0
	Get the body of the `INotification` instance.
virtual void	setType (int notificationType)=0
	Set the type of the `INotification` instance.
virtual int	getType ()=0
	Get the type of the `INotification` instance.
virtual	~INotification ()
	Get the string representation of the `INotification` instance.

Detailed Description

The interface definition for a PureMVC Notification.

PureMVC does not rely upon underlying event models such as the one provided with Flash, and ActionScript 3 does not have an inherent event model.

The Observer Pattern as implemented within PureMVC exists to support event-driven communication between the application and the actors of the MVC triad.

Notifications are not meant to be a replacement for Events in Flex/Flash/AIR. Generally, IMediator implementors place event listeners on their view components, which they then handle in the usual way. This may lead to the broadcast of Notifications to trigger ICommands or to communicate with other IMediators. IProxy and ICommand instances communicate with each other and IMediators by broadcasting INotifications.

A key difference between Flash Events and PureMVC Notifications is that Events follow the 'Chain of Responsibility' pattern, 'bubbling' up the display hierarchy until some parent component handles the Event, while PureMVC Notifications follow a 'Publish/Subscribe' pattern. PureMVC classes need not be related to each other in a parent/child relationship in order to communicate with one another using Notifications.