[thelist] cflock reads?
Chris Evans
chris at fuseware.com
Mon Jan 21 15:05:40 CST 2002
You need to lock the read in case of another page updating it, particularly
in the case of frames. You are correct, logically it should never happen,
but a "better safe than sorry" approach in CF code design.
Chris Evans
chris at fuseware.com
http://www.fuseware.com
-----Original Message-----
From: thelist-admin at lists.evolt.org
[mailto:thelist-admin at lists.evolt.org]On Behalf Of rudy
Sent: Monday, January 21, 2002 3:54 PM
To: thelist at lists.evolt.org
Subject: Re: [thelist] cflock reads?
> You might get concurrent session variable accesses if a user double
clicks
> a link (generating two http requests), or if someone publishes a URL that
> has CFID and CFTOKEN in them, everyone would be in the same session
okay, pete, thanks, i can dig that
it still does not explain why i have to *lock* the read of the session
variable
wouldn't all reads get the same value?
obviously i am super dense today
rudy
--
For unsubscribe and other options, including
the Tip Harvester and archive of TheList go to:
http://lists.evolt.org Workers of the Web, evolt !
More information about the thelist
mailing list