[thelist] CF: Keeping CFCs in application scope. Good or bad?

Mark Mandel mark.mandel at gmail.com
Tue Jul 20 08:26:22 CDT 2010


There should be no major problems with putting your CFCs in the application
scope.  You can easily store thousands of them (depending on your ram
limits) in there without too much difficulty.

Be aware that when you put CFCs in the session scope, every unique session
will get a copy of those, so I would limit those to CFCs that represent your
session state, i.e. something like a User object, etc.

You may want to look at a dependency injection framework like ColdSpring (
http://www.coldspringframework.org/) to help you organise your CFCs as well.


On Mon, Jul 19, 2010 at 4:25 PM, Frank Marion <lists at frankmarion.com> wrote:

> I've been re-doing a lot of my older stuff in CFCs lately. One question
> that I have is, how cool is it to stick most of the working CFCs in the
> application or session scope? On one hand, it would certainly make accessing
> functions quick and easy, on the other hand, I imagine that each application
> might suck up a lot of ram. This is on a shared server, so some
> consideration for memory space is, I think, in order.
> What are your thoughts?
> --
> Frank Marion
> lists [_at_] frankmarion.com
> --
> * * Please support the community that supports you.  * *
> http://evolt.org/help_support_evolt/
> For unsubscribe and other options, including the Tip Harvester
> and archives of thelist go to: http://lists.evolt.org
> Workers of the Web, evolt !

E: mark.mandel at gmail.com
T: http://www.twitter.com/neurotic
W: www.compoundtheory.com

cf.Objective(ANZ) - Nov 18, 19 - Melbourne Australia

Hands-on ColdFusion ORM Training

More information about the thelist mailing list