OO Principles: Separation of Concerns

Posted At : July 14, 2009 9:15 AM | Posted By : Steve
Related Categories: OO Principles

I don't "do OO" development in ColdFusion. I'm starting with that statement not to spark another debate about whether to use OO in ColdFusion, but rather to clarify that while this post is about a principle of object oriented development, you don't need to "Do OO" in order to learn, use, and benefit from separation of concerns.

In order for separation of concerns to work, your code really needs to be well encapsulated first.

What

Separation of concerns dictates that different modules of code overlap in functionality as little as possible. For me, this means that I have .cfm templates for output and .cfc components for logic and data retrieval.

[More]

Comments (2) | Print | del.icio.us | Digg It! | Linking Blogs | 7495 Views

Related Blog Entries

Comments (Comment Moderation is enabled. Your comment will not appear until approved.)
[Add Comment]
It sounds like you are using the MVC pattern. Have you ever used a ColdFusion framework to help you with that? I've never used a framework, but I'm interested in how other people use them.
# Posted By Ben | 7/14/09 9:49 AM
Ben,

Yeah, it did end up being a bit of an MVC pattern (not entirely by coincidence).

I have actually been using my own framework for a while. Once it is ready for prime time, I may blog a bit about it as well.
# Posted By Steve Bryant | 7/14/09 11:24 AM
[Add Comment]
BlogCFC was created by Raymond Camden. This blog is running version 5.8.001.