Putting CFCs in the App scope is perfectly acceptable. You just have to know that's where they're stored. With our enterprise app, we store about 2 dozen CFCs in various scopes. Server, App, Session, etc. Each stored in the scope most appropriate for it's use. It's helped us save memory, processing, and offers better performance.
-----Original Message----- From: Phillip Vector [mailto:vec...@mostdeadlygame.com] Sent: Thursday, September 24, 2009 4:19 PM To: cf-talk Subject: Re: CFC Question Yeah. I know. I'm not thinking today. Sorry about that. I didn't think it was that much of an issue. I think I'm going to use application.cfc and not try to put in CFC's into the application. It's to frustrating for not enough gain IMHO. On Thu, Sep 24, 2009 at 2:14 PM, Alan Rother <alan.rot...@gmail.com> wrote: > > Glad you found the issue... however in the future, disclosing a > valuable piece of information like, the fact you're running this code > inside a fusebox app would have cut this thread down to one or two emails... > > =] > > -- > Alan Rother > Adobe Certified Advanced ColdFusion MX 7 Developer Manager, Phoenix > Cold Fusion User Group, AZCFUG.org > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:326610 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
