Thanks everyone for your input. I think that I will add an init method. 1. It seems the best, most extensible way to do it. 2. It keeps my CFCs consistent. 3. There are no reasons NOT to do it. :-)
Thanks again. - JS ------------------------------------------------ Joshua Scott Resonant Media Technologies, LLC. http://www.resonantmedia.com | http://ponderings.wordpress.com "It is impossible to get out of a problem by using the same type of thinking that it took to get into the problem." -- Albert Einstein -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Phillip Senn Sent: Monday, May 08, 2006 3:24 PM To: [email protected] Subject: ** RE: [CFCDev] Init Methods on CFCs Joshua: Do you have anything hard coded, or are you assuming anything? For example, do either one of your functions use a hard coded Datasource name? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joshua Scott Sent: Monday, May 08, 2006 2:14 PM To: [email protected] Subject: [CFCDev] Init Methods on CFCs All, I have a two function utility cfc that I use to create sortable columns for record displays. Always before I have called <cfset var SortMaster = CreateObject("Component", "CAMSymphony.model.util.SortMaster") /> Many of the framework and OO oriented CFC patterns that I have seen actually have a init() method and are created like this: <cfset var SortMaster = CreateObject("Component", "CAMSymphony.model.util.SortMaster").init() /> I understand the purpose in the frameworks for using this pattern, but in a simple cfc is there a purpose for this? Any advise would be great. - JS ------------------------------------------------ Joshua Scott Resonant Media Technologies, LLC. http://www.resonantmedia.com | http://ponderings.wordpress.com "It is impossible to get out of a problem by using the same type of thinking that it took to get into the problem." -- Albert Einstein ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
