search

cs3org / OCM-API

OpenCloudMesh API
38 stars 11 forks source link

Existing standards #21

Closed labkode closed 1 month ago

labkode commented 7 years ago

There are already existing standards that we could use/be based on them:

For using WebDAV as synchronisation protocol there are already documents here: https://github.com/labkode/Internet-Storage-Sync/blob/master/applicability-of-webdav.md

Also, is worth looking into this for pros/cons of WebDAV vs REST for syncing:

moscicki commented 7 years ago

Here is the one currently used by owncloud and nextcloud: https://github.com/cernbox/smashbox/blob/master/protocol/protocol.md

DeepDiver1975 commented 7 years ago

Also, is worth looking into this for pros/cons of WebDAV vs REST for syncing:

WebDAV already provides a specification for Syncronization of resource collections: https://tools.ietf.org/html/rfc6578

This is the basis for CalDAV and CardDAV synchronization which from my pov has been proved to work in this aread for quite some years now.

dragotin commented 7 years ago

@DeepDiver1975 I haven't read through all the RFC so far, but do you know if it supports MOVE?

DeepDiver1975 commented 7 years ago

@dragotin https://tools.ietf.org/html/rfc6578#section-3.5.1 is explicitly talking about COPY MOVE and BIND - but there seems to be no explicit status/information on the operation.

Basically the result of this sync report is a list of changed (including added) and deleted resources.

For detection of MOVE we need to use additional properites like we do today with the fileid.

michielbdejong commented 1 month ago

Thanks for the mention of remoteStorage! :) Current OCM is multi-protocol for the actual resource sync, and we did another thorough analysis of relationship to OAuth and Fediverse recently so I think we can close this issue now.