I'm just playing devils advocate here, but...
I don't think this is what he is challenging. I thnik he is saying that it is possible (in an MVC architecture) to have different dependencies. Most articles, books, etc on MVC refer to the classical paradigm.Quote:
the view only ever gets data from the model. There is a reason for this: the model is the only place which holds data.
I think what Tony is adovocating, and I have to agree, is that in web-MVC ( http://martinfowler.com/eaaDev/PassiveScreen.html) the dependencies change quite substantially because of the request-response cycle, as opposed to real-time, event based based environements.
In passive view, the controller queries the the model and feeds the views, as opposed to the view having a dependency on any model. This creates a one-way dependency from the controller to the model and controller to the view, in theory making each component more reusable.
Of course, as you noted with the pager, this is not always the best approach, but it really depends on context, which is where I think Tony and you differ most.