> -----Oprindelig meddelelse-----
> Fra: sussman@collab.net [mailto:sussman@collab.net]
[snip]
>
> Morten Ludvigsen <morten_2ps_dk@yahoo.co.uk> writes:
>
> > If I understand you WebDAV does not specify what to do with a GET of a
> > directory, but it does specify what to do with a GET of a file
> ("internal
> > member" in WebDAV terminology).
>
> Correct.
>
> WebDAV/DeltaV doesn't have a concept of "HEAD revision". It has a
> concept called a baseline, which is essentially a snapshot or a tag in
> general SCM terms. In mapping DeltaV concepts to Subversion, we
> decided that mod_dav_svn would equate a baseline with a
> revision... but baselines aren't necessarily ordered. There's no
> necessary concept of the "latest" baseline in DeltaV. (gstein,
> baselines aren't necessarily ordered, are they? Not unless each VCC
> has a version history resource full of baselines!)
>
> In our particular implementation, we just *happened* to decide that
> the public URI space would represent the HEAD revision.... we're free
> to choose what we want public resources to represent. We didn't have
> to do that; we could have decided to have no public URIs at all. We
> could have decided that to get any file from *any* revision, you'd have
> to make a specific set of DeltaV queries... but we didn't. It seemed
> friendlier to make a public URI mean "the resource from the latest
> revision."
>
Yes - it is friendly. That is one of the (many) reasons why I have chosen
Subversion :-) Can I rely on this "friendliness" to stay the same?
>
> > In other words:
> >
> > 1. If I want to get the HEAD revision of the file
> > "/resource/slam.html" I CAN use
> > "GET [URL-to-repository-root]/resource/slam.html".
>
> Yes, because our implementation just happens to work that way.
>
> But if you want to write a 100% general DeltaV client, you'll need to
> use a set of specical queries to discover the "latest" baseline (I'm
> not sure if that's possible in general... gstein would have to say.)
Maybe in the future - but right now I am writing middleware that will
use Subversion as a read-only "database". All I need is to be able to
fetch a version (as in "tag" not "revision" :-) of a file using HTTP
and know that that version will never change.
For editing the files I will be using a normal svn client.
[snip]
> I think what I need to do is commit my "Summary-of-WebDAV" document to
> our notes/ area of the tree, for others to read. It should be much
> faster than plowing through RFC 2518 and 3253. Eventually, I'll merge
> this document into an updated version of our "How Svn uses DAV"
> document.
>
That would be beautiful. I have had a cursory look at the RFC's and they
is a bit overpowering :-) If I could read a summary then the RFC's would
probably be much easier to read.
Again, thank you very much for taking the time to reply at such length.
Regards,
Morten Ludvigsen
2-People Software
Denmark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 11 18:04:40 2002