- From: Clemm, Geoff <gclemm@rational.com>
- Date: Sun, 19 Aug 2001 23:53:34 -0400
- To: ietf-dav-versioning@w3.org
A server is of course free to refuse the DELETE request, and indicate as its reason that it didn't want to satisfy the postcondition that would remove that version URL from the DAV:merge-set. Note thought that even if the server allows the deletion, there is no race condition here, though, just some dangling version URL's that will return 404's when accessed. Cheers, Geoff -----Original Message----- From: Peter Raymond [mailto:Peter.Raymond@merant.com] Sent: Sunday, August 19, 2001 8:22 AM To: ietf-dav-versioning@w3.org Subject: Versions being deleted during a MERGE... Hi, I just noticed a potential problem with versions being used for a merge operation being deleted during the merge. Section 11 says a checked-out resource has a DAV:merge-set identifying versions to be merged. DELETE (section 11.5) says it will remove entries from the merge-set. Shouldn't the server disallow the DELETE, someone somewhere is in the middle of a merge using this version, also there would be a race condition if someone deletes the version while the client is processing the DAV:merge-set of a checked-out resource. Regards, Peter Raymond - MERANT
Received on Sunday, 19 August 2001 23:54:10 UTC