> Referencing the snippet below, taken from
> http://www.allaire.com/Handlers/index.cfm?ID=13810&Method=Full:
>
> My question is this: if CFLOCK is designed to prevent
> concurrency problems with session variables (among others),
> how much sense does it make to define a CFLOCK using a session
> variable?!?
>
> <cflock timeout="3" name="#session.sessionid#" type="EXCLUSIVE">
>
> I understand that the intent is not to duplicate the name
> parameter across users, but this seems a little against the point
> of CFLOCK.
Good catch! Actually, this has been discussed here in the past. This is the
reason the SCOPE attribute was introduced in CF 4.5.x. However, the Allaire
article hasn't been updated to reflect this.
If you're using CF 4.0.x, you should use an alternative naming scheme. For
example, if you're using cookies to associate a user with a session, you
could reference the values of those cookies.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
