Hi Gianugo,
where are you observing the DAV:checked-in property? PROPFIND should return the full qualified path /slide/history/50/1.0. (And for me it does)
But internaly slide works with its "namespace URIs" and stores them. Thats why in the database or if you are programming with the slide API you will find /history/50/1.0.
Stefan
Gianugo Rabellino wrote:
Yes it is the correct way, paired with DAV:checked-out.I'm wetting my feet with some shots at the versioning code and I'm a bit puzzled in front of what seems to be an incoherence in results.
While struggling to understand how am I supposed to get the current version of a resource, I stumbled into the DAV:checked-in property, which seemingly does exactly what I'm looking for. The problem I have, though, is that, when compared with the REPORT method results, I have different VCRs. REPORTs have this format:
/slide/history/50/1.0
while DAV:checked-in is formatted as
/history/50/1.0
This seemingly simple difference makes my life quite difficult, since I just can't rely on "slide" being the context path, my app needs to be portable across different setups (I'm version-enabling Cocoon's WebDAVSource, a very generic component), not to mention different webdav servers. So:
1. is checking DAV:checked-in the correct way to understand what the current revision is? Is there a better one?
2. is the formatting issue being solved somewhere I'm missing? Can it be considered a bug or does the spec dictate such a difference?
The spec does not allow or dicate such a difference. And for me PROPFIND returns the proper values.
Thanks for your help,
-- Stefan Lützkendorf -- [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
