Hello, I'm trying to clean up the mess left behind by the semi-secret forward-locking redux clusterf*ck in 4.1. Our base app needs to access files in our expansion APKs' assets/ directories. Apparently, the only way that still works after 4.1 is to use a ContentProvider.
As the whole ContentProvider machinery is a total overkill considering all I need is to access a bunch of files on a local SD card, I was pleased to notice the android:multiprocess attribute in the docs whose purpose should be expressly to mitigate the cost of IPC. However, it seems to do nothing actually, as is confirmed in this Google employee post: https://groups.google.com/forum/?fromgroups=#!topic/android-developers/u9UMJtALSXw I'm confused - a 2.5 years old post says it's "some old cruft" which unfortunately seems to be correct, yet current docs state otherwise? If 'android:multiprocess' really is obsolete, what is the replacement? Thanks in advance. -- -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
