Without getting too deep too quickly, as a general comment just remember that CFCs and custom tags are not functional equivalents, so it's not an either/or thing. CFCs are ColdFusion's version of objects and can be used to do object-oriented programming. Custom tags are a specific construct that's used within CF for a specific purpose. While there is certainly some potential overlap between the two, they're really two different animals and you'll use one or the other depending on what you're trying to do.
The way I do most of my applications now is to do relatively full-blown class models (aka domain models) in the system and use custom tags (via cfimport for more flexibility) to handle the logic on the UI/display side of things. I no longer use custom tags to do any backend logic. I'm sure you'll get lots of opinions and thoughts on this, and one of the great things about CFCs is that they've opened up all these possibilities. Just bear in mind that CFCs aren't a "replacement" for custom tags, and CFCs are far more than a construct to stick functions in. Likely you'll still use custom tags in your applications, they'll just handle different things than they used to. Matt On 9/8/05, Kevin Fricke <[EMAIL PROTECTED]> wrote: > > I have been using coldfusion for over 5 years but have not stepped into the > cfc realm yet. I know, I know, what am I waiting for.... > > Can someone briefly explain the benefit of a cfc versus a custom tag... > > Thanks, > > Kevin -- Matt Woodward [EMAIL PROTECTED] http://www.mattwoodward.com ---------------------------------------------------------- To post, send email to [email protected] To unsubscribe: http://www.dfwcfug.org/form_MemberUnsubscribe.cfm To subscribe: http://www.dfwcfug.org/form_MemberRegistration.cfm
