On 06/14/2010 12:00 AM, Olivier Guilyardi wrote: > On 06/13/2010 06:49 PM, tarek attia wrote: >> Thanks you so much for this clarification ,,exactly I want to make an >> application that keeps running while the user may went of the main >> application ,,and I guess Service will be the best candidate for doing >> that ,,,,,,, >> >> But what if the application will take much time ,,so should I make a >> thread that embedded inside it a Service?? > > Yes, exactly. If you need to do something heavy in the service, it must happen > in a dedicated thread, otherwise you will freeze the application main thread > (and thus the UI) which you should never do. > > So, you might need both a service *and* a thread.
Little clarification: of course this thread must be "embedded" in the service, not the opposite. The service acts as an entry point, in which you can create several threads if you like. -- Olivier -- 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
