> Indeed it does. But in all the instances I just saw (quick
> review), it was also doing a cfset, which absolutely MUST
> be locked.
>
> See, what I want to do is simply this:
>
> <cfif isDefined("Session.isLoggedIn")>
> <cfset Request.isLoggedIn = "y">
> <cfelse>
> <cfset Request.isLoggedIn = "n">
> <cfset Client.email = "">
> </cfif>
>
> Session.isLoggedIn is set within a cflock (obviously) on a
> valid login. After that, I include the above code in my
> Application.cfm and (maybe) do not have to incur a lock
> penalty. If defined, the session has not expired. I am not
> referencing the session variable itself, neither reading
> nor setting it. Just asking, 'Hey, are you defined?'. But
> maybe not. Err on the side of safety, I suppose.
Let me start by saying that I don't understand the internal operations of
the CF server. However, it would appear to me that the variable that's
actually being locked here is "Session", not "Session.isLoggedIn". If you
want to check for the existence of "Session.isLoggedIn", you have to touch
the Session variable and enumerate the keys within it.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
______________________________________________________________________
This list and all House of Fusion resources hosted by CFHosting.com. The place for
dependable ColdFusion Hosting.
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
