My advice is this, if you need to share information across users then use Application scope. Sure you will have to lock the variables, but it also means that less memory is being used by the system. Remember that client, session and normal variables take up extra space in ram. So if its duplicating information best to nip it there and then.
But designed correctly you can minimize the ram used, by looking at the application you are developing and then looking at what can be shared or could be shared across users. -----Original Message----- From: Won Lee [mailto:[EMAIL PROTECTED]] Sent: Friday, 9 November 2001 7:34 AM To: CF-Talk Subject: RE: Session variables To support Dave's email... On a conference call to Allaire, they recommended that I remove any instance of the Application scope. Their reasoning was that this would remove the need for locking (and the performance costs) and a more aggresive thread management. I wasn't allowed to ask them why or how. I was just told to do what Allaire told us to do. Actually I should be more specific. At a latter date I was told that they were not official Allaire people, but outside consultants that were representing Allaire. Either way, since that call I haven't seen a real reason to go back to using the application scope unless I really need it. I realize that a lot of people will email me saying, "Use the application scope, that's what it was meant for." I really don't know what to say to that. The truth is that the Application scope was created for persistent variables that run true over the whole program, but I'm rather happy with the performance gains and I'm also happy about not having to lock my variables all the time. I haven't tried this in a server farm environment though. Might be a bit different. Won -----Original Message----- From: Dave Watts [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 08, 2001 3:26 PM To: CF-Talk Subject: RE: Session variables > Good option, but the request scope is a memory killer - > Spectra is based on it and can suffer really bad performance > at times. There's nothing particularly more dangerous about the Request scope than about the local Variables scope, as far as I can tell. The Request scope isn't a persistent memory scope, like Session, Application or Server. While Spectra may suffer bad performance, there are lots of more likely reasons than Spectra's use of the Request scope. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusiona FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
