Hi Guys!

You might have encountered a few "autoversioning commits" in the past. Autoversioning is an Apache SVN Feature, which allows standard WebDAV clients to edit content via WebDAV.

If you didn't use WebDAV in the past, don't worry, so did I. But it is a powerful protocol, which is supported by a wide range of tools. There is even support in Linux to mount such a folder. But this is a feature which I would not recommend to use in combination with autoversioning (later more on that).

Delta V

If you search for WebDAV and SVN, you will come across the term "Delta V client". The WebDAV protocol didn't define version handling. So it was only well usable when it was used in a similar way as a public network share, by only few people.

The RFC3253 has introduced versioning features to the WebDAV standard. Clients supporting this addition are called Delta V clients.

SVN

SVN is using the WebDAV protocol as its HTTP/HTTPS based protocol. So an SVN client acts actually as a Delta V client. That's also rhe reason, why you can browse SVN repositories with a standard browser.

Autoversioning

The autoversioning feature is not specified in the protocol or even visible to the client. It is a feature, implemented by the apache webdav SVN module. It is very useful, as it gives you write access to an SVN repository with an ordinary WebDAV client, which doesn't know anything about versioning.

Use Cases

As mentioned above, WebDAV w/o versioning us only useful when you access it with only very few clients, as concurrent changea might not be detected, which can lead to loss of changes of one of the clients.