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

Re: Clarification on DAV server enforcing locks for PUT

From: Jim Amsden <jamsden@us.ibm.com>
Date: Tue, 27 Feb 2001 07:52:53 -0500
To: w3c-dist-auth@w3c.org
Message-ID: <OFF8F99CA6.073EA01F-ON85256A00.00467F56@raleigh.ibm.com>
There's no contradiction here. The first sentence says a WebDAV server
can't require all clients to use locking. The second one says that if a
resource is locked, then updates that don't include the lock token must
fail. That doesn't mean that clients issuing update requests without a lock
token will succeed on these locked resources, only that they may succeed on
unlocked resources.

                    "Steve K                                                                                
                    Speicher"            To:     w3c-dist-auth@w3.org                                       
                    <sspeiche@us.i       cc:                                                                
                    bm.com>              Subject:     Clarification on DAV server enforcing locks for PUT   
                    07:41 AM                                                                                

In reading RFC2518 section 6.7 "Usage Considerations", I think I'm reading
conflicting statements:

Paragraph 4 reads: "...it cannot force all clients to use locking because
it must be comparatible with HTTP clients that don't comprehend locking"
Paragraph 5 reads: "WebDAV servers that support locking can reduce the
likelihood that clients will accidentally overwrite each other's changes by
requireing clients to lock resource before modifying them..."

So can (or should) a DAV server enforce locking?

Steve Speicher
(919) 254-0645
Received on Tuesday, 27 February 2001 07:56:12 UTC

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