"From my understanbding, if you need to use a session variable throughout a given page, it is best practice to stick your session variables into a variable scope surrounded by locks."
says who? I would be putting it into the request scope. Lock it once and then reference everything through request but no, you dont need to lock cookie vars just remember if your testing to see if they exists, you need to use structKeyExists() Steve -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Chad Renando Sent: Tuesday, June 14, 2005 4:15 PM To: CFAussie Mailing List Subject: [cfaussie] C is for Cookie Been using session variables for a while, just getting into the whole cookie scope. From my understanbding, if you need to use a session variable throughout a given page, it is best practice to stick your session variables into a variable scope surrounded by locks. Does the same practice apply with the cookie scope, or can I reference my cookie variable willy-nilly throughout my application with no worries? Chad who just used "willy nilly" AND "no worries" in a technical coding forum http://www.randomhouse.com/wotd/index.pperl?date=19981208 --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
