Yes it is done by many poor coding developers. Request scope can be over used in certain scenarios, for example application and session when setting these up need cflocks, but when reading them they do not.
So a lot of developers tend to copy the application and session to the request scope, and I will ask why. Why would you want to place it in the application scope only to reference it via the request scope. Not only is this method memory hungry, but takes more processing time as the request is per request to the site, and your copying it to the request scope. Why not just use the damn request scope in the first place. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, 21 July 2005 11:11 PM To: CF-Newbie Subject: RE: Request scope I've used the Request scope to store application and session variables so that I don't have to do CFLOCK's constantly. I think this is done by many developers as I've seen several articles written on the subject. As for storing UDF's in the request scope, I actually haven't done that myself so I couldn't comment on whether it's encouraged or not. Dave -----Original Message----- From: Torrent Girl [mailto:[EMAIL PROTECTED] Sent: Thursday, July 21, 2005 8:59 AM To: CF-Newbie Subject: Request scope Have any of you used the request scope for things other than UDF's and is that encouraged? (I am trying to settle a discussion with a friend who uses the request scope for everything) TGirl ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:15:1323 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/15 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:15 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.15 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
