One of the big advantages of caching your CFC's in memory is to reduce the
overhead of instantiating them.
If you have a rarely used ADMIN section, then this wont be an issue for for
you if they are invoked every time you use them, so I wouldn't make any more
work for yourself unnecessarily.
...@michaels.me.uk]
Sent: Monday, March 28, 2011 9:22 AM
To: cf-talk
Subject: Re: cfc creation best practice
One of the big advantages of caching your CFC's in memory is to reduce the
overhead of instantiating them.
If you have a rarely used ADMIN section, then this wont be an issue for for
you
If you have a site or an area of the site that's not going to get used
a WHOLE lot would it make sense to create cfc objects (beans,
gateways, daos) when you need them or is it still best just to create
the gateway and dao object on application start? At what point would
you just create it in the
Since the memory footprint of a CFC is generally very small, I would just
create everything together at app startup (ideally using ColdSpring) and be
done with it.
On Sun, Mar 27, 2011 at 7:21 PM, Greg Morphis gmorp...@gmail.com wrote:
If you have a site or an area of the site that's not
Awesome! I appreciate the info Brian!
On Mar 27, 2011 9:48 PM, Brian Kotek brian...@gmail.com wrote:
Since the memory footprint of a CFC is generally very small, I would just
create everything together at app startup (ideally using ColdSpring) and
be
done with it.
On Sun, Mar 27, 2011 at
5 matches
Mail list logo
