> > 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.) >
I don't think so. Well at least I don't really know. It's higher level than that. All conflict management needs to be done on the client I believe. CloudKit is really just a cloud storage service, but rather than just storing files on a server, you store CKRecords which is just a key/value store. Pretty much the same as an NSDictionary. Values can be a variety of types including Strings, Numbers, Locations, NSData, and file attachments (CKAsset). Plus arrays of these types. CKReference objects are how you related objects together. I was thinking that if I store CBLDocument properties as an archived NSData and replace the existing corresponding CKRecord object in CloudKit, then when that's transferred to another device, I just use the regular putExistingRevisionWithProperties to store it locally and then I could call my regular code that processes conflicts. Right now I'm just picking the most recently modified document as the winner. -- 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/6e117d9e-418a-4380-9987-a0fd880b1c41%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
