- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 12 Sep 2002 22:13:44 +0200
- To: "Jim Whitehead" <ejw@cse.ucsc.edu>, "Gary Cowan" <Gary.Cowan@Tally.Hummingbird.com>, <w3c-dist-auth@w3.org>
> From: w3c-dist-auth-request@w3.org > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Jim Whitehead > Sent: Thursday, September 12, 2002 9:58 PM > To: Gary Cowan; w3c-dist-auth@w3.org > Subject: RE: Proposal: WebDAV and transactions > > > > > Well I suppose, but isn't this what wrapping updates with a > > Lock/Unlock pair is intended to accomplish. I have nothing > > against transactions, I just don't have any need for them > > spanning multiple WebDAV methods. Yet:) > > Lock/unlock doesn't give you rollback capability. Even though you're the > only person who can write to a resource during a lock, it still may be the > case that you're unable to complete the PROPPATCH part of a PUT/PROPPATCH > pair. The TCP connection may go down, the server may go down, you may be > exceeding your quota, etc. But a deltaV working resource does... So I'd claim that this *particular* use case already has a good solution. > ... -- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Thursday, 12 September 2002 16:13:48 UTC