That affirms a lot for me. Thanks!
Richard Schilling
Root Wireless
On Jul 14, 4:35 pm, Dianne Hackborn wrote:
> No, it will never be true.
>
> The VM doesn't manage processes at all. The system starts a process and
> runs a VM inside of it when it needs to run any components of an
> applicat
No, it will never be true.
The VM doesn't manage processes at all. The system starts a process and
runs a VM inside of it when it needs to run any components of an
application. Unless you specify otherwise, all of your components run in
the same VM, in the same process, sharing all of the same s
Yes. I had read that, and I understand that the VM tries to stratify
processes depending on their function and keep my process alive as
long as possible. What I'm really interested in is detecting when the
the VM (re)-instantiated and garbage collects my Activity class, and
how that relates to t
Yeah, the process lifetime, which is outlined here:
http://developer.android.com/guide/topics/fundamentals.html#proclife
On Tue, Jul 14, 2009 at 1:38 PM, Richard Schilling <
richard.rootwirel...@gmail.com> wrote:
>
> Thanks Dianne. Very helpful indeed.
>
> For process lifetime, I don't think yo
Thanks Dianne. Very helpful indeed.
For process lifetime, I don't think you're referring to the "entire
lifetime" of an Activity as defined on the API reference page for
Activity (http://developer.android.com/reference/android/app/
Activity.html):
"The entire lifetime of an activity happens bet
Statics are statics -- they are global to the process. So their value will
last for the lifetime of the process, which is usually much longer than an
individual activity instance.
On Tue, Jul 14, 2009 at 12:52 PM, Richard Schilling <
richard.rootwirel...@gmail.com> wrote:
>
> I just ran into a s
6 matches
Mail list logo
