Suffice to say, Presenter handles all the logic in the View, where as Mediator is supposed to be the View’s gateway to talk to others.

A Mediator isn’t supposed to “hold the View’s logic” although in smaller apps, he often does in the case of Mediators in PureMVC or Robotlegs. For some, they take it a step farther and clearly define the responsibilities, like Elad’s Presenter Robotlegs example.

So, while Presenter isn’t abused a lot, Mediator is… because in Flash, Mediator’s basically are Presenters in a lot of implementations I’ve seen.

For example, PureMVC & Robotlegs both “typically” have 1 View injected into the Mediator. Yet… the “Mediator” holds a lot of logic for the View, and allows it to communicate to other View’s via Notifications/Events. MOST implementations I’ve seen are like this. However, these “Mediators” suddenly take on a LOT of the View logic… thus making them act more like Presenters.

Read Elad’s article, that may give you another perspective. OR, check out how people are using the Passive View in Swiz. That’s a more evolved pattern that is especially suited to Flex devs who are wanting more guidance in their code behind implementations. Ben, who works on Swiz has one, and Brian Riley has a Part 1 and Part 2 example as well.

This is in reference to “talking to multiple views” or “one view”.