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

State of a lock

From: Julian Reschke <julian.reschke@gmx.de>
Date: Sun, 13 Feb 2005 14:43:39 +0100
Message-ID: <420F598B.5070204@gmx.de>
To: w3c-dist-auth@w3.org

Hi,

in 
<http://greenbytes.de/tech/webdav/draft-reschke-webdav-locking-latest.html>, 
I just extended the description of the status of a WebDAV lock to also 
contain information about the authenticated principal on whose behalf 
the lock was created. To clarify the role of "Lock Owner", I renamed 
that subsection to "Client-supplied Lock Owner Information". Both 
changes should now make it clear that the state of a lock indeed may 
include both pieces of information (which may have little relation to 
each other).

The new text reads:

2.5.5  Client-supplied Lock Owner Information (optional)

    Clients can submit information about the lock owner when creating a
    lock.  This information should be sufficient for either directly
    contacting a principal (such as a telephone number or email URI), or
    for discovering the principal (such as the URL of a homepage).

    Owner information is kept with the lock so that it can be returned in
    the DAV:lockdiscovery property upon request.  Note that this
    information is entirely client-controlled, thus a server MUST store
    the information faithfully just like if it appeared in a WebDAV dead
    property (see [RFC2518], section 4).

2.5.6  Lock Creator (optional)

    When a lock has been created by an authenticated principal, the
    server SHOULD keep information about that principal with the lock.
    This enables the server to subsequently check whether a lock
    identified by a lock token submitted in a request belongs to the same
    principal on whose behalf the lock was initially created (see
    Section 8.2.1 below).


(Change tracked at 
<http://greenbytes.de/tech/webdav/draft-reschke-webdav-locking-latest.html#rfc.issue.lock_state_auth_principal>).

Feedback appreciated,

Julian
Received on Sunday, 13 February 2005 13:44:27 GMT

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