> I don't see much use [for the request scope] beyond "A way to > avoid sending parameters to custom tags."
How about setting variables that are needed by nearly every request, and are used so frequently that locking the Application scope every time you need to read one would be annoying? I'm thinking of stuff used by <cfquery>: DSN, DB passwords, etc. The downside to this of course is the memory overhead with every request setting the same variables in memory for its duration. Obviously NOT nice for anything beyond low, low, low traffic sites. So I only use the Request scope like this for backend CMS's for small companies where there really are never going to be more than a few people in there at once. "What if the companies expand?" is the usual caveat. Well, I'm pretty sure the companies I'm talking about won't expand *that* much. And in the end, if they end up with problems with it, you just need to search the app for each mention of the Request vars you set, and convert it all to Application. Thinking of it, I suppose you could include a quick <cflock> and set a temp local var from the Application stuff in the snippet for a <cfquery>, so the annoyance of coding that for every DB query is cut down... So I guess that would be the way to go for real future-proofing. But I digress :) - Gyrus ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - [EMAIL PROTECTED] work: http://www.tengai.co.uk play: http://www.norlonto.net - PGP key available ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ______________________________________________________________________ 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
