Your point is understood. Encapsulation is a method though, not a rule. If we come up with methodologies and follow them blindly without knowing when the methodology helps us or cripples us... then we serve the methodology rather than the methodology serving us. That does not mean my concept is right... but could you chat with me about why you think this could be a detrimental approach?
My concept is to create a CFC that can call the core circuits settings, and actions. In CFMX the CFC is better at doing this than an UDF, or a Custom Tag. I don't have a problem with how Fusebox has done things... but for building sites it seems there is an easier way of doing things. The goal of the "methodology" used with this type of component is to have nTier focused applications. MVC is nice... and basically this is a parallel concept to MVC. Here is my questions... 1. Why would you have to do everything in a CFC to maintain encapsulation? 2. Would calling an include file be worse than calling a database or XML file because it contains logic? (nice nTier question) 3. If external logic is the issue... wouldn't dependence on an external CFC also break encapsulation? 4. For speed of execution, ease of implementation and debuggin, training, and such issues... can you think of an easier way to do things? Part of the success of any methodology is the ease of teaching it to others. If only a "well trained" developer can manage the site... then you have a big issue with Lifecycle management! Your thoughts are welcome, let me know where you would approach this differently. John Farrar ----- Original Message ----- From: "Brian LeRoux" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, August 06, 2003 4:00 AM Subject: RE: [CFCDev] Use of "instance" in 6.1 > // > > John, personally, I don't think cfinclude and cfc's should be in the > same sentence. :) The whole thing reaks of breaking encapsulation.. > > // ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
