Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Chris is correct in that TICoreDataSync just expects a plain hierarchical file system that you can access. While we don't have any other examples of using TICDS over another service (other than the iCloud feature branch) you would want to start by taking a look at subclassing <code>TICDSApplicationSyncManager</code>, <code>TICDSDocumentSyncManager</code>, and the NSOperations located in the <code>Generic Operations</code> group. You can read a little more about this in the updated documentation on the project wiki: <a href="https://github.com/nothirst/TICoreDataSync/wiki/Extending-the-Framework" rel="nofollow">https://github.com/nothirst/TICoreDataSync/wiki/Extending-the-Framework</a></p> <p>More specifically, let's say you wanted to sync over an Amazon S3 instance. You would create <code>TICDSAmazonS3ApplicationSyncManager</code> and <code>TICDSAmazonS3DocumentSyncManager</code> classes. Then, when registering your sync managers you would use those specific subclasses. The important thing to remember is that these service-specific subclasses only need to implement the communication layer of framework, all the syncing logic is handled in the super classes. Further more, the communication points are well defined.</p> <p>We recently released version 1.0.2 of the framework along with updated documentation, example apps, and tutorials on the project wiki. Check it out and if you run into any snags open an issue on the project's <a href="https://github.com/nothirst/TICoreDataSync/issues" rel="nofollow">Issues</a> page</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload