I am currently on the fence with either trying to implement this feature in couchbase lite or using couchbase lite + url links in the documents to pull attachments on demand.
What would be the minimum feature set that I could implement in couchbase lite that would be considered as the start of an API? I would hope to avoid changing the sync gateway under a first implementation. On Tuesday, May 5, 2015 at 11:15:06 AM UTC-7, Jens Alfke wrote: > > > On May 5, 2015, at 10:45 AM, Brett Harrison <[email protected] > <javascript:>> wrote: > > As an optional feature, has it ever been considered to pulling attachments > on demand? And not pulling them during sync, or pulling them in a very low > priority mode? I know this kind of conflicts with offline operation, but I > can see a use for it if a database grows large with attachments. > > > Yes, we've talked about this, but it hasn't been implemented. It would be > a major win, but it also needs a fair amount of API — configuring which > attachments should be lazy, requesting an attachment, monitoring download > progress, canceling, etc. > > —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/f16e931f-ee46-4c4c-9193-73980b4364bd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
