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

RE: Working collections

From: Clemm, Geoff <gclemm@rational.com>
Date: Sun, 19 Nov 2000 23:40:38 -0500
Message-ID: <3906C56A7BD1F54593344C05BD1374B10120D400@SUS-MA1IT01>
To: ietf-dav-versioning@w3.org
> From: Geoffrey M. Clemm [mailto:geoffrey.clemm@rational.com]

> One way to think about this is that I'm suggesting that checking
> out a collection version should create a workspace (i.e. a tree
> of version selectors), or in other words, that a working collection
> is a workspace.

Something I blithely glossed over with this proposal was the fact
that a version selector needs a target, and checking out a collection
version gives you the target for a version selector for that collection,
but does *not* give you targets for version selectors for members of
that collection.  This would have to be done by the client, with
either a SET-TARGET (e.g. with a Depth header and a label)
or a MERGE (e.g. with a baseline).  So the sequence would be:

- create a new workspace by checking out a collection version
- set the targets of the version selectors in that workspace
  with either a SET-TARGET or MERGE request
- do whatever CHECKOUT's, PUT's, DELETE's, CHECKIN's etc. you
  want to version selectors in that workspace.
- DELETE the workspace when you are done (or leave it around if
  you think you might be doing more work in that collection later.

This does require two extra requests (the SET-TARGET or MERGE to
get started and the DELETE when you are done), but that does not
seem like an unreasonable amount of overhead.

Received on Sunday, 19 November 2000 23:41:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:46 UTC