Trait ruex::prelude::Notification

source ·

pub trait Notification<Body>: Debugwhere
    Body: Debug + 'static,{
    // Required methods
    fn interest(&self) -> Interest;
    fn set_body(&mut self, body: Option<Body>);
    fn body(&self) -> Option<&Body>;
}

Expand description

The definition for a PureMVC Notification.

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, Mediator 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 Command’s or to communicate with other Mediator’s. Proxy and Command instances communicate with each other and Mediator’s by broadcasting Notification’s.

A key difference between native 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.

Should implement fmt::Debug to get the string representation of the Notification instance