Re: The version-tree report for version history resources

This is a multipart message in MIME format.
--=_alternative 0040A530852571DB_=
Content-Type: text/plain; charset="US-ASCII"

Note: A better answer (:-) would have been:

If your server supports the version-history feature, then the version-tree 
report is unnecessary, since you can do a DAV:expand-property report on 
the DAV:version-set.

Cheers,
Geoff

--------------

Yes, that would be very reasonable, but note that in practice it is much 
more likely for the client to have in hand a URL for a VCR or a Version, 
on which a version-tree report is defined.


Werner wrote on 08/31/2006 05:54:58 AM:
> Shouldn't the version-tree report also apply to version
> history resources when the version-history feature is
> supported? It seems like the most obvious resource to
> ask it to.


--=_alternative 0040A530852571DB_=
Content-Type: text/html; charset="US-ASCII"


<br><tt><font size=2>Note: A better answer (:-) would have been:</font></tt>
<br>
<br><tt><font size=2>If your server supports the version-history feature,
then the version-tree report is unnecessary, since you can do a DAV:expand-property
report on the DAV:version-set.</font></tt>
<br>
<br><tt><font size=2>Cheers,</font></tt>
<br><tt><font size=2>Geoff</font></tt>
<br>
<br><tt><font size=2>--------------</font></tt>
<br>
<br><tt><font size=2>Yes, that would be very reasonable, but note that
in practice it is much more likely for the client to have in hand a URL
for a VCR or a Version, on which a version-tree report is defined.</font></tt>
<br>
<br>
<br><tt><font size=2>Werner wrote on 08/31/2006 05:54:58 AM:<br>
&gt; Shouldn't the version-tree report also apply to version<br>
&gt; history resources when the version-history feature is<br>
&gt; supported? It seems like the most obvious resource to<br>
&gt; ask it to.<br>
<br>
</font></tt>
--=_alternative 0040A530852571DB_=--