If I converted them to objects I would likely be using them the same way that I do now, at least for the short term. The app is one that's been up and working for quite some time. The CFCs are stateless right now. I hadn't considered making them stateful, but that wouldn't be a bad idea either.
-----Original Message----- From: Dave Watts [mailto:dwa...@figleaf.com] Sent: Friday, October 22, 2010 9:46 AM To: cf-talk Subject: Re: OOP vs cfinvoke > I've got an app here that has several hundred cfinvoke calls to a couple > of CFCs. I'm trying to decide if it's worth my time to go through and > convert the app from using cfinvoke constantly to using cfobject. How > much of a difference on my overhead will it make? It entirely depends on how CFINVOKE is being used, and whether you'd be able to use CFOBJECT/CreateObject in a different way. If the CFCs are stateless, would it make more sense for them to be stateful? If they're already stateful, is CFINVOKE being used to return and reuse an instance of the CFC? Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsite. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:338482 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
