| Excerpt |
|---|
Documentation of the different operation primitives that the protocol describes |
Introduction
Common for all operations is that they follow the flow described in Message flow and that all operations are targeted at a specific Collection, the only exception is the GetStatus operation as it regards components.
...
The descriptions of the various operations here does not cover the exact details about the expected behavior and corner cases, but just the broader conceptual parts. Details are kept in integration tests and acceptance tests in the reference code for two reasons:
- To ensure documentation and reality (implementation) does not drift apart
- Enable automatic verification of components and their interaction.
Describe that details about expected behaviour in various situations is kept in integration tests to ensure documentation does not drift apart from realityThe tests can be found here.
| Children Display | ||||
|---|---|---|---|---|
|
Single data object for get, put, delete and replace
It is only possible to perform get,put,replace and delete operations on a single file.
The reason for this choice is to have a simple protocol. Requests on multiple data objects would complicate data transmission of the different files as well as error handling.