I like to think that its not model view controller, but instead model-view-behavior (or the strategy pattern)

Events are a given. Models can fire/handle events, views can fire/handle events. The behavior/strategy pattern is just a bunch of singleton objects that know how to mediate between the view and the model. Sometimes the behavior pattern handles events (as a strategy), but it doesn't fire events (only the model and view can do that).

The model knows how to generate the behavior. The View contains the behavior and asks the behavior questions with the model.

This separates responsibilities nicely in my opinion.