Why not let the sesion var do it's thing and communicate / check the application var and register itself (make itself known) and check to see if it should be on the server or not, etc. You could then use the application var to 'kill' the session variable if need be (a nice and neat little "boot" command).
Just curious, ~Todd
At 11:08 AM 5/29/2003 -0400, you wrote:
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.
Thanks,
Nelson
---------- Todd Rafferty ([EMAIL PROTECTED]) - http://www.web-rat.com/ Team Macromedia Volunteer for ColdFusion http://www.macromedia.com/support/forums/team_macromedia/ http://www.devmx.com/
----------
----------------------------------------------------------
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).
