On Fri, Oct 22, 2010 at 2:26 PM, Eric Carman <[email protected]> wrote:
> We were hoping to move the setup/firing of these downloads into a
> thread.

Correct. IntentService has its own background thread.

> Although the scenario above seems to work just fine (via testing/
> logging), we are probably not able to accept the additional exposure
> that the threads get flushed when service ends and the OS sees them as
> more eligible to get rid of.

Correct. Do not leak threads after the component that forked them is destroyed.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

_The Busy Coder's Guide to Android Development_ Version 3.1 Available!

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to