Re: target selector again
jamsden@us.ibm.com
Tue, 5 Oct 1999 11:04:59 -0400
From: jamsden@us.ibm.com
To: Jeff_McAffer@oti.com (Jeff McAffer OTT)
cc: ietf-dav-versioning@w3.org
Message-ID: <85256801.00530DBC.00@d54mta03.raleigh.ibm.com>
Date: Tue, 5 Oct 1999 11:04:59 -0400
Subject: Re: target selector again
Maybe the Target-Selector should be a RSR, i.e., a list of revision selectors.
We also talked about a "path of revision selectors" to specify the revision
selector for each element in the URL path. All this was to avoid mangling the
URL with things like http://host:8080/foo@2/bat@33/index.htm@25.
We may also want to associate a context with a user that could include his
workspace, current activitiy, etc. This is effectively what "local mode" does.
But this is becoming pretty stateful. If the collections aren't versioned, then
there is no issue though.
Jeff_McAffer@oti.com (Jeff McAffer OTT) on 10/04/99 05:10:36 PM
To: ietf-dav-versioning@w3.org (ietf-dav-versioning)
cc:
Subject: target selector again
Tim and I were just talking about the Target-Selector and wondering what
it really means to specify a revision-id? Of what resource is this
revision-id? If it is for the resource at the last segment of the
Request-URI, what selector is used to select the resource's parents? The
default workspace? What if I need to specify my workspace?
It seems that reasonable arguments could be made for using workspaces or
labels in the Target-Selector but revision-ids don't seem to work. What
was the reasoning for having it?
Jeff and Tim