Hello Warwick, Actually, according to the deltaV spec and from what I've seen in my Slide limited past experience, whenever we create a new resource, a new history node must be created. It doesn't really matter if the resource shares the same URI.
That raises a problem witch is, how to garbage-collect the orphan nodes? The spec does not mandate any action on these nodes, and Slide seems to it likewise: seems like that client should take an option, on how to handle them properly. Best regards, Miguel Figueiredo ________________________ Hi, I haven't investigated this real deeply but I was wondering if there a reason why the structure of the /history folder doesn't mirror the hierarchy in the content space? eg. for a file /files/fileA the history folder would be /history/files/fileA with the fileA versions under it. Is it because the delta-v spec says that you can't delete the VHRs for a VCR even when the VCR is deleted? And so if the VHRs are left around and you try to create a new file with the same name and path after deleting it the first then the old history would still be around and mess things up? Thanks, Warwick --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
