How high up a structure should you name your locks?

[PaulKD]

This is another one of those late night "locking - do i need them?" questions:-

I use application variables extensively - based on userids

e.g. application["user"]["u#userid#"]["LastAccess"]

When I want to change the LastAccess I normally use a named lock -
name="u#userid#"

Should I be calling the lock "user" or given that userids are unique and the
chance of a user managing to corrupt their application variables is remote - do
i even need the lock?

Good answers greatly appreciated.

[Adam Cameron]

> This is another one of those late night "locking - do i need them?" questions:-

The most common answer these days is "no".

Read this:
[url]http://www.houseoffusion.com/cf_lists/index.cfm/method=reply&forumid=4&threadid=39328&messagecount er=201028[/url]

> I use application variables extensively - based on userids
> e.g. application["user"]["u#userid#"]["LastAccess"]
> When I want to change the LastAccess I normally use a named lock -
> name="u#userid#"

application["user"]["u#userid#"]["LastAccess"] = now(); // is this what you
mean?

If you're using CFMX or above, you don't need to lock that. Java does it
under the hood for you.

--

Adam