W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > October to December 2001

Eclipsed resources...

From: Peter Raymond <Peter.Raymond@merant.com>
Date: Tue, 23 Oct 2001 15:03:52 +0100
Message-ID: <20CF1CE11441D411919C0008C7C5A13B02CFAC25@stalmail.eu.merant.com>
To: ietf-dav-versioning@w3.org
Hi,

The deltav draft (section 14.1.1) says that a non version-controlled
resource can 
"eclipse" a version-controlled resource.  When the non version-controlled
resource
is deleted or moved the version-controlled member is exposed.

I have a few questions/issues regarding this concept:

1) What happens if a VERSION-CONTROL request is issued on the non
version-controlled
   member that is eclipsing the version-controlled resource?

2) BASELINE-CONTROL can be issued with a baseline URL in the request body
(in order to
   populate the collection), if there is a non version-controlled resource
at the 
   destination whose binding name clashes with the name of a member in the
baseline does 
   eclipsing occur?  It seems like the same scenario but eclipsing is not
defined here.

3) Why was this defined this way around? Surely the version-controlled
member should
   take precedence over the non version-controlled resource.

4) Why was this behaviour defined instead of just failing the UPDATE or
MERGE request.
   This eclipsing behaviour seems odd and it may confuse end users to have
their resources
   masked by some other resource.

Does anyone in the group have any good material explaining the "hows and
whys" of eclipsed
versions? How did it get into the spec in the first place, was there use
cases etc?

Regards,
--
Peter Raymond - MERANT
Principal Architect (PVCS)
Tel: +44 (0)1727 813362
Fax: +44 (0)1727 869804
mailto:Peter.Raymond@merant.com
WWW: http://www.merant.com
Received on Tuesday, 23 October 2001 10:05:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:42 GMT