MVCR pattern (was Re: [Catalyst] Bing!)

Perrin Harkins perrin at elem.com
Fri Aug 12 00:05:16 CEST 2005


On Thu, 2005-08-11 at 17:27 -0400, David Storrs wrote:
> 1- "conceptual model":  The picture I have in my head of how  
> something should work.
> 
> 2- "pattern Model": The element 'Model' in the MVC pattern.  A purely  
> conceptual object that exists only in mindspace.  Similar to 'Linked  
> List', or 'Binary Tree'.
> 
> 3- "Model library": The code that actually manipulates data--talks to  
> a database, holds state, whatever.
> 
> 4- "framework Model": The code which implements the role of Model  
> within a particular framework (e.g. Catalyst).  So far as  
> manipulating the pattern Model goes, the framework Model does not  
> need to be more than a empty wrapper around the Model library; the  
> only thing the framework Model needs to provide is hooks that allow  
> it to easily talk to the rest of the framework.

There is no difference between 3 and 4 in my mind.  Code that glues
together your model implementation with the rest of the framework is
supposed to be a part of the framework itself or unnecessary.  I've
never need to write any with any framework I've used, beyond the usual
"use Foo" and calling normal methods.

- Perrin




More information about the Catalyst mailing list