W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > January to March 2003

RE: Visibility of a Workspace

From: Clemm, Geoff <gclemm@rational.com>
Date: Sun, 19 Jan 2003 23:07:42 -0500
Message-ID: <E4F2D33B98DF7E4880884B9F0E6FDEE201A121C4@SUS-MA1IT01>
To: ietf-dav-versioning@w3.org

VERSION-CONTROL with a specific version argument creates
a VCR that refers to the existing version and its version
history.  This is what lets multiple workspaces work on the
same version history concurrently.  See postcondition
DAV:new-version-controlled-resource:
"a new version-controlled resource exists at the request-URL whose
DAV:checked-in property identifies that version"

Cheers,
Geoff

-----Original Message-----
From: Vikram_Roopchand [mailto:Vikram_Roopchand@infosys.com]
Sent: Sunday, January 19, 2003 3:30 AM
To: ietf-dav-versioning@w3.org
Subject: RE: Visibility of a Workspace



Hi,
   When it is said that a vcr is created in a workspace by VERSION-CONTROL
request and initialized with another version from some other version history
, does that mean that 
this vcr also "point's" to the same version (and thus is part of the same
tree ) or is altogether
new with it's own vr and history (of that vr). 

e.g:

VERSION-CONTROL /foo.html HTTP/1.1
Host: ...
.
.
.

<?xml .....>
<D:version-control ...>
	<D:version>
		<D:href> http://server/someotherhistory/12/ver/3 </D:href>
	</D:version>
</D:version-control>

so is foo.html pointing to ver/3 or is totally new with it's vr having
history as v1 ?

I believe it is the latter , but I am quite confused at this moment to
reason.

Thanks a lot,
Vikram
 
Received on Sunday, 19 January 2003 23:08:14 GMT

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