Quick tip - if you don't want to make your own key with CFID_CFTOKEN, don't forget you can use session.urlToken, which is the same (well, I believe it's cdid=#cfid#&cftoken=#cftoken#, but it serves the same purpose).
======================================================================== === Raymond Camden, ColdFusion Jedi Master for Mindseye, Inc (www.mindseye.com) Member of Team Macromedia (http://www.macromedia.com/go/teammacromedia) Email : [EMAIL PROTECTED] Blog : www.camdenfamily.com/morpheus/blog Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Nelson Winters > Sent: Thursday, May 29, 2003 9:08 AM > To: [EMAIL PROTECTED] > Subject: [CFCDev] CFCs in Application vs. Session scope > > > I'm working on an application in which I'm instantiating a > CFC for each user in the Application scope: > > application.Users["#CFID#_#CFTOKEN#"] = > createObject('component', 'path_to_my_cfc.cfc_filename'); > > These objects are handling quite a bit of processing per > request. I'm storing these in the application scope rather > than in the session scope that I can loop through > application.Users and clean up objects that have been opened > longer than the desired limit. The application won't have > more than 100 users in any given hour. > > If anyone is aware of any pitfalls that I may encounter doing > things this way, or know of a better way, let me know. At > this stage, it wouldn't be too difficult for me to change > things around if I have a good reason to. > ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
