RE: error condition for delete of VHR when VCR is in checked-in c ollection from Tim Ellison on 2002-07-09 (ietf-dav-versioning@w3.org from July to September 2002)

From: Tim Ellison <Tim_Ellison@uk.ibm.com>
Date: Tue, 9 Jul 2002 14:17:32 +0100
To: ietf-dav-versioning@w3.org
Message-ID: <OF923D7855.5A2F19D0-ON80256BF1.00486402@portsmouth.uk.ibm.com>

Julian wrote:

> b) the server deletes the VHR and un-version-controls the
> VCR (to avoid breaking the live versioning properties).

In what sense would the property be "broken"?  Clearly from the server's
point of view there is a good reason why it may not want to so this, but
from a protocol point I don't see a problem.  For example, what would be
the difference if the version-history resource is unaccessible due to other
circumstances, such as authentication or reachability?

The semantics of a version-controlled resource can be enforced even if the
version-history resource does not exist.

Regards,
Tim

Received on Tuesday, 9 July 2002 09:18:02 UTC