[thelist] CF Session Variables

Joshua Olson joshua at alphashop.net
Tue Oct 2 15:35:27 CDT 2001


I don't know the answer to the first question, but maybe I can shed some
light on the second.

My understanding is that the name attributes provides a unique identifier to
the lock.  When you lock with a name, it will be single threaded with all
other locks with the same name on a server wide scale.  This way, you are
not locking the entire session scope on the server like you would if you
just said scope="session"

If you lock the scope "session", then all locks of scope "session" within
the application will have to wait for you to close the lock before they can
continue.  But, if you use a specific name, then only those locks with the
same name as the lock in question have to wait.  This is much more flexible
than locking an entire scope.

The docs say that scope and name are exclusive... don't use both attributes
in a single lock. This makes sense.

Also, we discovered a while back that you should not do a cflocation within
a cflock as it does not always release the lock.

-joshua

----- Original Message -----
From: "Glenn Hunt" <ghunt at hds.ca>
Subject: RE: [thelist] CF Session Variables


: Why is this safer on a 4.5.1 box (as opposed to 5, I assume). What is
: the difference between a NAME= and SCOPE= anyway? I've always been a
: little fuzzy on this.
:
: Glenn Hunt
: ghunt at hds.ca





More information about the thelist mailing list