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

RE: HOW_TO_IDENTIFY_LOCK_OWNER

From: Jason Crawford <ccjason@us.ibm.com>
Date: Tue, 8 Jan 2002 17:53:49 -0500
To: Daniel Brotsky <dbrotsky@adobe.com>
Cc: w3c-dist-auth@w3c.org
Message-ID: <OF2A7F8BBE.5FB10042-ON85256B3B.007C3FDE@pok.ibm.com>

All,
   Dan and Lisa have suggested that we need to more clearly define either
the use of the lockowner field or that we need a way to identify the owner
of the lock.

  http://lists.w3.org/Archives/Public/w3c-dist-auth/2001JulSep/0218.html
says...

> > (Especially because the spec provides
> > no way to reliably determine who owns a lock.)

> This is a good point -- and this is already a failing of WebDAV, with or
> without UNLOCK_BY_NON_LOCK_OWNER.  Clients that crash or miss the
response
> from the server need to make sure that the lock is theirs before grabbing
> the lock token using PROPFIND.  Can lockowner be used for this purpose?

> This should be a separate RFC2518 issue.  How about
> "HOW_TO_IDENTIFY_LOCK_OWNER".

Just as a point of information, I'd like to point out we have an issue on
the issues
list that is somewhat related: DEFINE_PRINCIPAL.
In that issue Mark D Anderson says:

  The term "principal" is never defined in the WebDAV
   specification, or the HTTP or Digest specifications.
   It should be defined.


Lisa and Dan,
  Could you define the requirement before we start the discussion?  For
example, is it for the server or the client that we need to make the
clarification below?  (I'll reference your clarfication from the issues
list.)

J.



------------------------------------------
Phone: 914-784-7569,   ccjason@us.ibm.com
Received on Tuesday, 8 January 2002 18:11:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:59 GMT