Jacob, I believe that is what Barney meant. The biggest time hit is processing the CFC and getting and instance "instantiated". After it is instantiated (if you cache it in "scope" then it's not going to be much more than just execution speed... which should be quite fast. (Barney isn't that what you meant?)
John -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Munson, Jacob Sent: Monday, August 22, 2005 1:28 PM To: [email protected] Subject: RE: [CFCDev] Better way than dao, gateway, bean: <cfquery> Well, that's all fine and good. But what about processor time? I've heard that CFCs make a significant hit to the processor when compared to just running code in the page. Its probably negligible for just one or two CFC calls, but if you are calling 10 CFCs in a page, and those CFCs are in turn invoking others, it could add up quick (probably exponentially). ---------------------------------------------------------- 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). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
