thanks Jeffry - Kinley
>From: Jeffry Houser <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: CF-Talk <[EMAIL PROTECTED]> >Subject: Re: Session variables >Date: Thu, 08 Nov 2001 09:59:54 -0800 > > That is confusing. I think perhaps even a bit misleading. > > My understanding is that session variables reside in a shared memory >space. The reason for using CFLOCK is to prevent multiple accesses to that >shared memory space, because they can get in each other's way and corrupt >data. I do not understand why frames would have any affect on it. > > FYI, I have heard of experiences with inconsistent results when two >developers have been working on the same site (separate code) and not >locking session variables. If it can happen on a site w/ two people.. it >can happen on a site w/ more than two people. > >At 12:18 AM 11/08/2001 -0800, you wrote: > >I am totally confused... > > > >In "Mastering Coldfusion 4.5 by Arman Danesh": > > > >"Although session variables are not shared between clients, it is still > >possible for one client to have multiple threaded access to a session > >variable. This could occur if frames are used, or if the user decides to > >reload or refresh the page." > > > >Is this true? Session variables are not shared between clients. I should > >only be using <CFLOCK> tags when session variables are being used within > >frames. > > > >What is the normal rule of thumb? > > > >Totally confused... > > > >Help! - Kinley > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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
