I like your pseudocode, but I’m not sure that I completely agree with it. When I’m developing my iPhone apps, the View does not recieve a reference to the Model. I think this has to do with the idea that each of the three key objects in MVC should be portable and message based. This allows the view to be applied to other models.

I would look at the difference between figures 4-5 and 4-6 at this site:
http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaFundamentals/CocoaDesignPatterns/CocoaDesignPatterns.html

4-5 sounds like the MVC design pattern that you’re referring to, where the View has a reference to the Model. However, Cocoa (and I believe Cocoa Touch) use what is in 4-6, where the Model only interacts with the Controller.

This is the type of discussion I’ve been looking for. Thanks!

Actually, the model should not understand any of the other constituent parts in the MVC pattern. The view holds a reference to the model. The controller will reference both the model and view. Sometimes the view and controller are conflated into just the view. The model is unaware of anything but itself. It may, however, trigger events for other classes who are in an Observer relationship with it.

So you’ll have pseudocode that looks like this:

Model theModel = new Model(); //notice how it doesn’t know about any other classes?
View theView = new View(theModel); // to get state from the application
Controller theController = new Controller(theModel, theView0; // to control application logic and flow

I’m still figuring out MVC in iPhone-land because it looks a bit different in this environment than in others (which is actually how I found your blog post). Best of luck!