- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sat, 8 Mar 2003 20:17:28 +0100
- To: "Lisa Dusseault" <lisa@xythos.com>, "'Jason Crawford'" <nn683849@smallcue.com>
- Cc: "'WebDAV'" <w3c-dist-auth@w3.org>
> From: w3c-dist-auth-request@w3.org > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Lisa Dusseault > Sent: Saturday, March 08, 2003 8:07 PM > To: 'Jason Crawford' > Cc: 'WebDAV' > Subject: RE: Move and Delete (was: bind draft issues) > > > > > I second what Jason said -- based on the lack of client support for > "propertybehavior" I'd like to see a couple client implementors say they > would implement a feature which would allow them to choose, on some > servers supporting atomic MOVE/DELETE, whether to force that behavior or > not. We do. > A light-weight approach is that since some servers will be atomic and > some won't, merely define some string in a header or body in response to > OPTIONS which says "I do atomic delete always" or "I don't always do > atomic delete". Clients may or may not use that information, but at > least it's really easy for a server to advertise. I think this approach is too simple. Whether a MOVE will be atomic or not may depend on source, destination and state of resources. That isn't something I want to compute upon OPTIONS. Julian -- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Saturday, 8 March 2003 14:17:46 UTC