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 and datatx protocols compatibility is ensured by keeping the same property name uri (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 for sharedKey?
That's right, talk is a "protocol" on its own, and I can obviously take responsibility to align Reva's webapp support to OCM 1.2 if we go ahead with this PR.
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
?