What Is Model-View-Controller?
According to James Dempsey’s “Model-View-Controller Song,” MVC is a way of organizing your code into “functional segments so your brain does not explode.” MVC divides your application into three layers, each with a clearly defined task: Model The Model contains all of the business logic and data in your application. It is not a stretch to say that your Model literally is your application. Typically, a Model consists entirely of objects or services such as CFCs, Java classes, and / or Web Services. A Model never has any knowledge of Views or Controllers. View A View is what the user sees, and is how the user interacts with your application. The View’s job is to allow user input and display the “state of the Model,” an Object-Oriented (OO) way of saying “your application’s data.” Most often, Views are traditional ColdFusion pages (.cfm). Other mediums such as Flash can also act as views. Because your Model isn’t aware of the Views, you can interchange views without affecting your overall
