Re: [Storagesync] recent issues discussed (plain text)

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

hi，
End users may be more concerned about the improvement of the upload rate. According to the report in"http://testmyiphone.com",  the average downstream throughput is more than 4490 Kbps, the average upstream throughput is only about 869 Kbps.


----------------------------------------------------------------------------------------------------------------
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 issues vs metadata
    i.is mainly for identifying whether a document is changed or not
    ii.is easy to implement than that of WebDAV sync protocol or not
    iii.the metadata file contains all etags for all files at both client and server side or not
  f)the distributed peer model (no server) and C/S mode
  g)a fancy example (with pics) of OfflineIMAP’s sync process in following URL