This would be the case with any shared-scope variable, not just a CFC. Overall, I doubt that using a CFC instead of a something like an array of structures in the session scope makes much of a difference as far as memory used. Yes, it will use more, but the difference should be minor. However, I know of no way to quantify the difference.
As far as instantiation time, yes it will be higher than if you didn't use CFCs at all, but since it only happens once (on session creation) this shouldn't be much of an issue either. RAM usage shouldn't go up when the user logs off and logs back on, as their previous session variables would simply be replaced with new ones. Hope that helps, Brian -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Chabot Sent: Tuesday, July 13, 2004 1:50 PM To: [EMAIL PROTECTED] Subject: Re: [CFCDev] CFC size ...I do know that if I make a change to the CFC file, the person has to log out then log back in to see the change, which hints at a potentially larger than expected RAM usage and object instantiation time because of the use of CFCs. Thank you, Mike Chabot ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
