components that are common only to a specific app and these are stored in
application scope. I guess some unlucky person has to wait a minute or so
for them to compile every few days. These CFCs are for database interaction
as well as for things like validation. User specific things are stored in
session scope. I think I am actually saving on server memory usage since
there is only on CFC for DB interaction per application in server memory,
not 1 for each user.
TK
-----Original Message-----
From: Michael Hodgdon [mailto:[EMAIL PROTECTED]
Sent: Friday, December 05, 2003 11:35 AM
To: CF-Talk
Subject: question about which memory scope to load cfc's
I am working with a website structure that will have five to seven
separate applications. As I start to plan which CFC's will perform tasks
necessary for each website, I am also noticing functionality that would be
useful for all applications. For instance, if you create a database.cfc to
pull queries that are based on data that all websites will need (for
instance company information) would it be appropriate to stick that cfc in
server memory?
I guess my question is a best practices question regarding storing CFC's
in server memory.
Thanks in advance.
Michael
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
