The mediator is only concerned with events that require it to perform some other request. It may be to get data from a proxy and set it on the component, or to send a notification that accomplishes some other task (via a command or some other mediator listening for it). The rest of your views should send and receive events as they normally would in any none "frameworked" app. You don't want to route everything through the mediator, only things that require some action to be performed by other PMVC actors (Proxy, Mediator and Commands).
Cool, that's what my impressions were; stuffing everything in the mediator would be kinda messy given the role which has been assigned to a mediator i.e. mediation. Thanks for confirmation.
BTW, just so that we have the technicalities cleared up, what reason do you think I should present if I'm giving a PureMVC session and someone ends up asking "
Why aren't all the events directed to the mediator? What practical harm might come of it other than the normal 'it is not a job of the mediator'"?
One reason that I can think of is that, the more "view" specific code in the mediator, the more difficult it becomes to port the mediator if the view changes given the high dependence of the mediator on the view. Any other reasons you can come up with?
TIA,
sasuke