Next message: Geoffrey M. Clemm: "Re: move/copy/delete/etc in a change set"
Date: Thu, 10 Aug 2000 13:22:25 -0700
From: Greg Stein <gstein@lyra.org>
To: ietf-dav-versioning@w3.org
Message-ID: <20000810132225.F19525@lyra.org>
Subject: Re: move/copy/delete/etc in a change set
On Thu, Aug 10, 2000 at 04:07:13PM -0400, Geoffrey M. Clemm wrote:
> From: Greg Stein <gstein@lyra.org>
>
> It is still a teeny bit unclear of the actual form of the HTTP requests to
> accomplish these items. However, I'll be working on that over the next few
> days. I think that I'll develop a sequence of req/resp matching my example
> change set below, and then post it back here for review/comment.
>
> Great! Tim has been working on a scenarios document, but currently
> it just has core versioning scenarios (no workspaces, no activities,
> no version-controlled collections), so we need to get advanced versioning
> scenarios added.
Ah. Good call. Yes, I'll see that my example/scenario gets sent to Tim for
inclusion into the scenario doc (at least as a start).
> For example, one of my questions to work through is: what URL do you use for
> a PUT to place a new resource into a checked out collection? Do you PUT
> under the working resource?
>
> Yes.
Gotcha. Thx.
>...
> Do you PUT under the version selector and the
> server automatically goes to the working resource and alters it?
>
> For workspaces, effectively the answer is "yes", but not because
> you did your PUT to the version selector, but rather that the
> server replaced your version selector with a working resource.
>
> In core versioning, there can be multiple working resources associated
> with a single version selector, so it would be ambiguous which one to
> go to.
Right. Makes sense.
> Now I personally would prefer to just say that every version selector
> is in a workspace, and that you can only have one checkout of a given
> version selector (and that's what our implementation will do), but
> that's just me (:-).
Bleck. "just me" says that a separate header to be used as a URL prefix is a
hack :-)
[ there is also the requirement of the WS URL needing to be distinct from
all non-WS URLs; I find that a problem since I'd want the WS to mirror the
live URL space; but I don't want WS anyhow, so this is moot :-) ]
Well in any case. Thanx for the pointers. I'll have a scenario worked up by
Monday.
btw, what I'm doing is mapping Subversion's (http://subversion.tigris.org/)
operating model onto DeltaV. The design is due Monday :-). After that, I get
to start coding. Theoretically, I should have a DeltaV-based Subversion
completed by November/December. (actually, I'm reasonably confident as I
made up those numbers myself :-)
Cheers,
-g
--
Greg Stein, http://www.lyra.org/