hi mathias,
Maybe i should clarify on the question about obtaining the version given the
uri to the version-controlled-resource.
I understood the mechanism you used to generate the URI for the version
given the URI for the version-controlled-resource and the version number.
But how can a client obtain the URI for a revision given the URI for the
version-controlled-resource.In other words when you automatically do a
checkout\checkin on a resource when the client issues a proppatch or a put
request do you return the URI of the created version in the Location Header
for the client to use it?
thanks,
rajkumar
-----Original Message-----
From: Luber, Mathias [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 18, 2001 5:05 AM
To: '[EMAIL PROTECTED]'
Subject: version controlled resources and version resources
> -----Original Message-----
> From: Raj Kumar [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 17, 2001 7:57 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Delta V so far (WAS: RE: Implementation of Delta V)
>
>
> hi mathias,
> Thanks a lot for your reply.
>
> With your implementation can you retreive the content and
> the contents of a specific version rather than the version controlled
resource ?
First of all: I can agree with Remy. It is possible to retrieve a specific
version by its unique URI.
But more interessting (for me) is to put the question the other way round:
"Can I retrieve the version controlled resource rather than a specific
version?"
I have to say: Currently there is no chance to retrieve the version
controlled resource, if it's checked-out.
But let me explain, why I think there will not arise any problems at the
moment. For Basic Versioning Feature we only know the additional methods
version-control and report.
So I think that there are only two values for auto-version, which will make
sense: DAV:checkeout-checkin and DAV:checkout-unlock-checkin. The other two
possible values will not make any sense, because they will require a checkin
by the user, which is not implemented in Basic Versioning Feature.
I think this will guaranty that the version controlled resource is always
the last version in the linear versiontree (=last version). All webdav
methods in slide are acting on the last revision in NodeRevisonDescriptors,
which is in fact our last version. So if there is no version specified in
the request, it will work automatically on the version controlled resource
(which is in our case the latest version).
Anybody with me this far and can agree to this?
> For example how can a client retreive the content of specific version
given
> the version controlled resource?
I think the mechanism explained in my last mail will do so. But it may be
that I didn't get your question right.
> With your current mechanism used to generate a URI for the
> version is the version also http accessible (I am not sure)?
I already imlpemented it in Slide server and client. It works.
>
> I would appreciate your help on this.
> thanks,
> rajkumar
Thank you a lot for asking! Your questions show me where I have to take a
closer look at.
So please keep on asking,
Mathias
