Some people will disagree with me, but here goes: In theory, if you are setting enough application variables (let's say 10 for the hell of it), it makes sense to set them one time only and only run request.foo = duplicate(application) on every request. This would be marginally better than setting 10 request vars on every hit. Of course, 10 is a number I pulled out of thin air.
In general, if you are setting a few variables, I'd say to just set them in the request scope. Maybe you lose 1ms per hit, but I'd be willing to bet that for 99% of us, this won't impact performance in any significant way. That being said - be aware that what I saw above will NOT apply to every one and every site. Like most things performance-related: details matter. ======================================================================= Raymond Camden, ColdFusion Jedi Master for Macromedia Email : [EMAIL PROTECTED] Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda > -----Original Message----- > From: Critter [mailto:[EMAIL PROTECTED]] > Sent: Monday, July 08, 2002 2:58 PM > To: CF-Talk > Subject: Application vs Request........ > > > oi CF-Talk,!! > > ok don't flog me.. but since most app variables are > locked and set to a > request scope......is there any loss of "performance" or > is just putting all > app scoped variables as request scoped variables in > the application.cfm > acceptable...? > > etc etc > > -- > Critz > Certified Advanced Bald White Barefoot ColdFusion Developer > > Crit[s2k] - <CF_ChannelOP Network="Efnet" Channel="ColdFusion"> > > ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
