Improve share access process and share examples #158
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is an attempt to fix #157, but in doing so it partly breaks the v1.1 protocol to access a share.
In particular, for the
webdav
anddatatx
protocols compatibility is ensured by keeping the same property nameuri
(resp.srcUri
), but the recommended value is now a simple identifier or "key", not a full URI.For the
webapp
protocol I propose to break compatibility, assuming that the only implementation that requires to be adapted is Reva.This is still work in progress as I'm myself not fully happy, the main outstanding question being shall we actually drop
uri
and go forsharedKey
?