Greg Stein's new WebDAV usage document says:
> Subversion uses a tree-based format to describe a change set against
> the repository. This tree is constructed on the client side to
> describe the change. It is then marshalled to the server,
> reconstructed, and applied against the repository. However, WebDAV
> uses a sequence of changes. As a result, we must map from the tree
> form to a sequence of WebDAV requests, send them over the wire, then
> reconstruct the tree form on the server for application to the
> repository.
I don't understand, even at a high level, how this is going to work.
Is the server going to completely ignore the WebDAV-specified
semantics of the sequence of requests, construct a tree, and then
process them in a subversion-specified manner? Does this actually
qualify as "using WebDAV?"
For that matter, WebDAV doesn't appear to have the concept of a
sequence of requests, just individual requests. How do we delineate
the beginning and end of a sequence? (And, as before, doesn't this
break the WebDAV model a whole lot?)
Received on Sat Oct 21 14:36:06 2006