I'd sure hate to write a SOAP webservice in a .cfm file. Also, cfm files don't give you objects that can be passed around, provide encapsulation of data, and support code re-use via inheritance and method overriding. I mean, you can do anything you want in cfm files, but there are some things that are just way cleaner and easier in a component if you want to drink the koolaid and change your paradigm. CFCs can be used as glorified include files with no ill side affects, but if that is all you are doing with them it's kind of like starting your microwave on fire to cook your supper over it. :) ~Brad
-------- Original Message -------- Subject: CFC's.. Why use them? From: Phillip Vector <[email protected]> Date: Tue, September 08, 2009 9:39 am To: cf-talk <[email protected]> Besides the code being reusable, is there a specific reason why I should use a CFC rather then a CFM file? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:326093 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
