If there was (I don't think there is), since the bundle is normally a zip file, it would expect that would mean that the framework was copying the zip entry into a file, so I don't see how you would be gaining anything time-wise, perhaps just a tiny bit less code?
david jencks On Dec 12, 2014, at 9:14 AM, Benson Margulies <[email protected]> wrote: > I've got code that makes extensive of memory mapping. I'm wishing that > I could make a bundle that contained a large data resource that could > be memory mapped. > > One path I see involves a copying process: expect to get a URL to it > by getEntry() on a bundle, and then copy it into a file path from > getDataFile(); once copied, it would persist. My question: is there > any way to avoid the copy? Is there anything in the manifest that > would cause the framework to plop the data someplace reachable with a > File? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
