WEBDAV CLIENT WITH CHECKOUT CAPABILITY TRIAL

These variations in supported functionality can only be discovered through trial and error and much examination of property values.Ĭertain features are arbitrarily defined in the DeltaV specification as 'Basic' features. Another example is that if the server forbids checking out a version that already has a successor, the server does not support branches. For example, if the server never allows the auto-version property to be set to a value, that implies that the server does not support automatic versioning at all.

In addition to the advertised features, major functionality differences can be inherent in how servers allow and forbid operations and property values. DeltaV only requires that the server 'should' support one of the defined packages, so supporting a package is not strictly required. None of the packages can be advertised (in OPTIONS response or elsewhere), so the client must look for each feature involved in a package to see if the server supports the package.

In an attempt to deal with this issue, several packages were defined a package is a set of features. The DeltaV authors realized that the abundance of optional features presented a problem: No client could be expected to interoperate with all the possible variations of server functionality (there are 2 10 theoretical combinations of advertised features). There are 11 named features, and only one (the version-control feature) is required. Support for each feature can be advertised in the OPTIONS response by including the feature name in the DAV: header. In DeltaV, the functionality that can be offered is divided into named features.

Webdav client with checkout capability