Hi Jens et al, I'd like to be able to provide my customers with another way of syncing their devices. Currently I'm providing Cloud sync via IBM Cloudant and Nearby Sync using peer-to-peer syncing in CBL 1.3.
But many of my customers would prefer to use something like iCloud or Dropbox for syncing. In fact, I just released the new version of my app after a year in development switching over to Couchbase Lite and I've been roasted in the app reviews because I dropped support for iCloud and Dropbox syncing. So I"m trying to find a way to get it back yet still be able to have all the advantages of Couchbase Lite, which is a fantastic framework of course. I already have code in my app to generate an archive file using CBLDocument's putExistingRevisionWithProperties, so I know how to work with that. But I was wondering what the viability of using that method would be to provide a file based sync solution? What I mean by that is I would take incremental snapshots of the changes made since the last time a sync operation occurred, then I would store the change file in iCloud Drive or Dropbox and then on the other device, read the changes file and process it using putExistingRevisionWithProperties. It would have to be able to handle deletes, updates, and new documents. Does something like that sound viable? I'm thinking that it is as long as I can get a list of documents that have changed recently and if those documents contain the isDeleted flag. It seems like it's a possible solution for me. Any comments, ideas, or concerns with implementing something like this? Thanks! Brendan -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/22578849-dc4d-4f8b-9087-05fac8bc0252%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
