> > I think you could build a sync system using CBL where the clients > communicate *only* through CloudKit. The revision tree stuff in CBL would > just be unused overhead. But you can’t combine this with CBL’s replicator — > I’ve tried to figure out how to, and it just doesn’t work. If revisions can > get transferred both through CloudKit [or something similar] and through > the normal replicator, the versioning can get seriously confused and Bad > Stuff can happen, like false conflicts and clobbered writes. >
I think that's ok. I would basically be giving customers the ability to choose CloudKit OR (Cloudant and/or Nearby sync). So if they choose CloudKit then it won't be using any of the CBLReplicator stuff. But I'm assuming I would still use the call to putExistingRevisionWithProperties to store the data from CloudKit to the local database, providing the ordered set of revision history IDs and attachments? -- 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/4a0f9bef-f2b4-4da3-b681-d5f9563d6ef5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
