I think you can make this work, but keeping track of document versioning will be difficult, especially in the case of conflicts.
This is actually similar to some design work I’ve been doing this year for future versions of Couchbase Mobile. I have some good mechanisms designed for replicating to servers that can’t store extensive metadata like revision trees … but the implementations are not yet solid enough to actually try out. Unfortunately I haven’t had a chance to dig into the details of CloudKit, so I can’t give any detailed advice. Does it have some sort of MVCC mechanism that can prevent a writer from clobbering a change made by another writer? For example something like the ETag mechanism in HTTP (i.e. PUT with If-Match.) —Jens -- 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/1CB6C71D-4987-4752-AF56-859CF0CA428D%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
