[Storagesync] recent issues discussed (plain text)

["Fei Song" <[e-mail]>]

Here is the latest version. Please email me if anything is missed:
 
1.The design targets of WebDAV, rsync and other existing approaches?
2.The potential use cases of ISS, such as client/server, git-like pattern, svn, etc.
3.The efficiency improvements might be the second goal for standardizing ISS protocol
4.CORS headers on storage sync APIs
5.What is needed for the ISS: a sync protocol or a generalized API
6.remoteStorage draft discussion
  a)relationship vs WebDAV
  b)MOVE action (synchronization) should be added or not
  c)Beside web browser, desktop apps (by hacking way)
  d)comics of new standard
  e)etag is mainly for identifying whether a document is changed or not
  f)the distributed peer model (no server) and C/S mode
7.GitHub instead of email messages (has been created) with following URL:
  https://github.com/labkode/Internet-Storage-Sync
  a)What is the topic? 
    i.Whether it is suitable to build on WebDAV
    ii.WebDAV vs remoteStorage
    iii.Advantages vs disadvantages of WebDAV
8.Metadata and data separation scheme and platform for synchronization
  a)ownCloud when configured to use an Object Storage as the Primary User Storage. (Metadata is handled by a MySQL database)
  b)CERN EOS Storage System. (Metadata is handled in high performance in-memory structures).
  c)DropBox. (As far as I know it uses S3 behind. For metadata it is unknown, but probably not on S3). 
    Paper for analyzing DropBox:
    http://annasperotto.org/papers/2012/imc140-drago.pdf
  d)ClawIO will have an implementation of this approach in the next phase using Swift.


Some related organizations, events, projects, etc.: 
GEANT community, OpenCloudMesh, ownCloud, CS3, remoteStorage, ClawIO, crosscloud, Dropbox, CERN EOS Storage System, to be added…