RE: [CFCDev] MVCF at benorama.com

[Barney Boisvert]

Title: Message

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Scott Barnes
Sent: Monday, March 24, 2003 5:01 PM
To: [EMAIL PROTECTED]
Subject: RE: [CFCDev] MVCF at benorama.com

 <snip />

 

Its all good, no matter the outcome so long as you typically keep your presentation layer, business logic and data layer all separate and independent of each other, you really can't [EMAIL PROTECTED] things up? 

 

And this is exactly what MVC is, a model (data), a controller (business logic) and views (presentation).  MVC is not a code format, it's an very high-level ideal for code architecture.  There are a million solutions, some bad, some good, some more explicit, and some a very non-enforced coding style, but all MVC.  So whether you call it that or not, you typically use an MVC architecture already, albiet one that isn't explicit as most.  it's when you start building a framework that explicitly forces MVC upon you that developers start complaining, even though they already program in the style.  However, enforcing the MVC design pattern is usually a good thing for two main reasons (that I see), it allows other developers to more easily jump into a project mid stream, and it provides some cross-checking to make sure you aren't cutting corners when you shouldn't (even though all developers do).

 

<snip />