On Wed, May 30, 2012 at 12:20 AM, Dianne Hackborn <hack...@android.com> wrote: > On Tue, May 29, 2012 at 9:10 AM, Latimerius <l4t1m3r...@googlemail.com> > wrote: >> >> Yeah, I know, a standard idiom using temporary files actually relies >> on this, I was just pondering how come someone has (tens of) my asset >> files open that I myself haven't touched. > > > There aren't tens of files open, there is one file -- the .apk. All "files" > you are talking about are just entries inside of that zip file.
Oh, I had no idea that installed applications aren't even unzipped. I really think it's about time to root a phone to see how things are done under the hood. :-) > What you are indeed seeing is just standard Linux filesystem semantics where > the storage for a deleted file is not reclaimed until nothing is using it > any more. In this case, creating the Context on the .apk has opened that > .apk for read access, and the Linux filesystem will not allow its storage to > be removed until it is closed. Hm, that however means the behaviour is well-defined and reliable. At least until installation start to include unzipping. -- 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
