An alternative approach is to use a static field to pass the data. This SO post <http://stackoverflow.com/questions/12819617/issue-passing-large-data-to-second-activity> shows one of the better (IMHO) ways of implementing this.
I've seen other discussions about using weak reference maps to achieve this in a slightly more flexible way. This is one aspect of Android I find frustrating. Intents and Parcelables use Binder. Binder passes data in and out of kernel memory. Unnecessary copies are unpleasant. Being limited by kernel memory space is unpleasant. Using globals/singletons is pretty clearly not so great either. It will make code harder to read and maintain. It's a lot easier to write, and has much less overhead than Parcelables, though. Hod On Thursday, July 28, 2016 at 8:15:51 AM UTC-7, Nenad Stojnic wrote: > > Hi. > > Problem description: > Activity_A have one Meta object which contains two fields > com.couchbase.lite.Document and Map<String, Object>. > We need to send Meta object from Activity_A to Activity_B and then we edit > Meta object in Activity_B. > We want to do it using Intent. > Meta object must be Parcable. > How can we make that Meta Object is Parcable? > > -- 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/2f6933f9-97e4-4a34-8561-faeae70d4de8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
