Friday, April 28, 2006, 11:23:22 AM, one spoke: NS> Yes, for this example, it's an overkill. If you're setting session NS> variables to a static value to be read later, there's no reason to NS> lock. If you're setting it in a few different places and rendering NS> of pages depends on it being one value or another, you may want to NS> get creative with your locking, and finally, if you're setting NS> complex structures in the session, like
What I'm actually doing in that space is logging in an admin based on whether they're logged in in a different application, so it's a "write-once if not written" ... The question was more about crossing sessions than what's going on inside the session (doing things in a function in app.cfc sorta "feels" like doing something in application scope). -- Jim Flannery [EMAIL PROTECTED] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
