W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 2002

RE: What is left after LOCK/UNLOCK on null resource?

From: Michael Leditschke <mike@ammd.com.au>
Date: Thu, 5 Sep 2002 14:34:45 +1000
To: "Clemm, Geoff" <gclemm@rational.com>, <w3c-dist-auth@w3.org>

> The new process needs to obtain its own (new) lock.  The old
> lock is cleaned up by a timeout, or if allowed by the server,
> the new process can clean up the old lock with an UNLOCK.
> The new process shouldn't "reuse" the old lock, unless you have
> some way of guaranteeing that two processes cannot both reuse the
> old lock at the same time.

And if the lock were exclusive with an infinite timeout? A lock
on an already locked resource will fail. Isn't lock re-use the
only option apart from Administrator intervention?

Is it fair to say the locking model is more oriented to 
transient locking rather than long term locking?

Received on Thursday, 5 September 2002 00:34:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:26 UTC