Your description is right on target with regard to request scope. Wasn't aware of the point Peter brought up about request being the default.
Request scope is a local scope, like the variables scope, which unlike request does NOT persist to CFMODULE or custom tag calls. Its just handier to reference a local var as a request var by default. You would want to use the variables scope for local vars that you expressly did not want to cross template lines, so to speak. Otherwise I think request is just the flavor of choice for a local var. ----------------------------------------- Matt Robertson [EMAIL PROTECTED] MSB Designs, Inc. http://mysecretbase.com ----------------------------------------- ----- Original Message ----- From: "Terry Hogan" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Saturday, November 10, 2001 5:45 PM Subject: Request Scope Questions I've been trying to brush up on my CF skills and I'm a bit confused with Request Variables. I've been through Ben Forta's CF5 Construction Kit and Danesh CF4 books and I only see reference to Request Variables in discussions of Custom Tags as a variable type that can be shared and changed by both the custom tag and the calling template. That makes sense to me, if I understand it correctly. But I have also seen the Request Scope mentioned on this list and in sample code in other contexts. Some defining Application variables such as datasource name and User Access data. So I guess my question are: 1. What exacty is the Request Scope? 2. How are Request Variables similar or different from Session or Application Variables? 3. When should/shouldn't Request Variables be used? 4. What about locking? I've read that Request Variables don't need to be locked. Is that true? Why not? TIA Terry ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
