> On Sep 29, 2017, at 7:35 AM, devlist <[email protected]> wrote: > > However if attachments are added later on then the entire thing will be re > uploaded. > A suggested optimisation would be to check the previous revision and just > upload attachments that have a new signature?
It already does this. Each attachment tracks what revision it was added/modified in (it’s a “revpos” attribute in the JSON) and the replicator only transfers attachments that have a newer revpos. So I don’t understand why the attachments would be transferred multiple times, unless you were re-adding every attachment in each revision. What does the document JSON look like, in the original code where you created multiple revisions? —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/FCA7E14A-0990-409C-9381-603106BCB4CC%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
