Unlocking notifications (BugZilla issue 259), was: [Fwd: Gen-art last call review of draft-ietf-webdav-rfc2518bis-17.txt]

Julian Reschke schrieb:
> ...
>> s6.6, para 3: 'notifications should be sent': Is this supposed to be a
>> function of webdav?  This is the only mention of lock notifications in
>> the document.
> 
> This text has always been in the spec, but you are the second one to
> complain.
> 
> Opened issue
> <http://ietf.osafoundation.org:8080/bugzilla/show_bug.cgi?id=259>.

Proposed text change:

Proposed Change:

Section 6.6., para. 3:
OLD:

    If the timeout expires then the lock SHOULD be removed.  In this case
    the server SHOULD act as if an UNLOCK method was executed by the
    server on the resource using the lock token of the timed-out lock,
    performed with its override authority.  Thus logs should be updated
    with the disposition of the lock, notifications should be sent, etc.,
    just as they would be for an UNLOCK request.

NEW:

    If the timeout expires then the lock SHOULD be removed.  In this case
    the server SHOULD act as if an UNLOCK method was executed by the
    server on the resource using the lock token of the timed-out lock,
    performed with its override authority.  For instance, if the server
    implements some sort of logging and notification system for locking-
    related events, a lock timeout should be treated similar to an UNLOCK
    request.

(See also 
<http://ietf.osafoundation.org:8080/bugzilla/show_bug.cgi?id=259> and 
<http://greenbytes.de/tech/webdav/draft-reschke-webdav-rfc2518bis-latest.html#rfc.issue.bz259>).

Best regards, Julian

Received on Sunday, 25 February 2007 18:53:00 UTC