PureMVC Framework for Haxe: API Documentation
Back | Index
class org.puremvc.haxe.patterns.observer.Notification
implements org.puremvc.haxe.interfaces.INotification

A base `INotification` implementation.

PureMVC does not rely upon underlying event models such as the one provided with Flash.

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. 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 `Notification`s to trigger `ICommand`s or to communicate with other `IMediators`. `IProxy` and `ICommand` instances communicate with each other and `IMediator`s by broadcasting `INotification`s.

A key difference between Flash `Event`s and PureMVC `Notification`s is that `Event`s follow the 'Chain of Responsibility' pattern, 'bubbling' up the display hierarchy until some parent component handles the `Event`, while PureMVC `Notification`s 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 `Notification`s.

function new(name : String, ?body : Dynamic, ?type : String) : Void
  Constructor.
function getBody() : Dynamic
function getName() : String
function getType() : String
function setBody(body : Dynamic) : Void
function setType(type : String) : Void
function toString() : String

Back | Index