Check it out at http://www.actionscriptdeveloper.co.uk/puremvc-tutorial-flex-puremvc-jabber-and-xiff-3-introduction/

Enjoy,

Dave Keen
http://www.actionscriptdeveloper.co.uk

I do see this behavior is accepted by PMVC best practice document. Quite possible that the logic involving multiply proxies should be put into the Command. I have to make it very clearly; you know, in a development team, if no convention or discipline in our mind, folks tend to adopt shortcut by putting all logic in Mediator, which results an useless Control tier.

There is an advantage to putting application logic in a command object as you can swap out a command if you decide to handle user gestures in a different way. This is in line with the intended purpose of a controller in the MVC pattern. The controller should be a “strategy” for handling user gestures (i.e. concrete strategy in a strategy pattern). In contrast, code modifications would be required if the logic was in the Proxy.

Accessing the proxy through a command in all cases is theoretically sound but it does introduce an additional command object. Keeping the number of commands down to a manageable level should also be a consideration.

In the sample app “EmployeeAdmin” on PMVC website, the mediator access proxy to update data, quite a few times. Don’t understand why they did this!