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

RE: Resolving outstanding issues in DeltaV

From: John Hall <johnhall@evergo.net>
Date: Sun, 24 Jun 2001 13:07:48 -0700
To: "'Clemm, Geoff'" <gclemm@rational.com>, <ietf-dav-versioning@w3.org>
Message-ID: <000201c0fce9$578fdf40$0400a8c0@xythosjohnhall>
> [mailto:ietf-dav-versioning-request@w3.org] On Behalf Of Clemm, Geoff
> From: Lisa Dusseault [mailto:lisa@xythos.com]
> A garbage collector that deletes objects that still have 
> references to them is as much of a bug (and arguably, more of 
> a bug) than a garbage collector that misses some objects.

Missing objects is fatal.

Deleting objects that have references, in a loosely coupled system where
the references are understood to be conditional (files on the web --
ever seen a broken link?) is a feature.

>    Solutions to problem 1 might involve something like a "orphaned
>    resources report" that allowed the storage losses to be "found".
> 
> Such a report is reasonable (and we certainly will be 
> providing a custom report of this kind for my server), but 
> since this report is independent of the current feature set, 
> I would not suggest holding up standardizing on the current 
> set of features in order to reach consensus on the semantics 
> and protocol for this report.

This report would not cause changes to the current feature set, but
without it the feature set is not complete without additions.  Is
completeness required to be a draft, or just relative stability?
Received on Sunday, 24 June 2001 16:07:51 GMT

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