I have the same issue when using couchbaselite-phonegap-plugin(1.1 with SG 1.1,REST API). and at the same time, I also want to know, How should I do on the CBL side. I can accept the sync gateway's doc, but how should I do ? a) delete the CBL's conflict doc and let sync gateway sync the doc again? the deletion will tiger the sync back to sync gateway from CBL? the version of doc in CBL will increase? b) Using the sync gateway's doc to update the CBL's doc? the version of doc in CBL will increase? and this will cause other conflict(also if the doc's rev will generate by doc's value,but the rev will include 2 part,such as in CBL ,the rev is 3-f1f92da1ac57cb812b5352aca4272ff6 and in the sync gateway ,the rev is 5-f1f92da1ac57cb812b5352aca4272ff6)?
On Thursday, July 16, 2015 at 12:19:53 AM UTC+8, Jens Alfke wrote: > > Generally it’s assumed that the app and server should agree on validation, > so that the app cannot produce a revision that the server rejects. In other > words, the validation done by the server is to mostly protect against > malicious clients trying to send bad data, and also to guard against bugs > in legitimate apps. > > If the app produces a revision the server rejects, it’s in kind of an > awkward state, since the user could have made that change a long time ago > (while offline). It’s a bad UX to have to say “Oh, that edit you saved this > morning? I just realized it’s not valid, so do it over.” The app should > have done its own validation at the point the user pressed Save, and > presented the error then. > > But you have a point that, if this did happen, the app might want to know > about it. It would be pretty easy to have the replicator post a > notification. (In general, I think there’s a need to have the replicator > post finer-grained progress information, and this is a part of that.) > > Could you file an issue requesting this, please? > > —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/3c7a8992-670f-4729-bf6a-76f2bb731572%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
