Is there anything wrong about putting those background tasks on threads? That's how I've been doing it so far. I don't need these tasks to do any IPC and my Runnables already support Lifecycle logic (implemented by me initially for other java project)
On Apr 9, 9:11 am, Mark Murphy <mmur...@commonsware.com> wrote: > Donal Rafferty wrote: > > The singleton wont be killed by the system automatically like a service > > which could lead to GC problems > > Correct. Objects held in static data members, or referenced from a > static data member, will not be garbage collected. Hence, you need to > remember to null out those static data member references. Services, on > the other hand, will garbage collect automatically, assuming you do not > put one in a static data member yourself. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > Android Training in US: 14-18 June 2010:http://bignerdranch.com -- 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 To unsubscribe, reply using "remove me" as the subject.
