Depends. But since the OP mentioned Notifications, i guess the search results should be presented even when the user left the application. If so, yes, then a Service would be best.
Still, i would use an AsyncTask (inside the Service) to do the actual work. This way you'll be sure that the client's call to the Service will never be blocking. On Apr 14, 3:20 am, MobDev <developm...@mobilaria.com> wrote: > I am just making a wild guess here, and I hope more experience people > will support or deny it (Mark, are you awake yet ? ;) ) but this might > be a good scenario for a Service ? > > On 6 apr, 16:21, jfbaro <jfb...@gmail.com> wrote: > > > > > Hi, > > > I am working on a simple application (studying purposes) which list > > all the files from a selected folder. On top of that I would like to > > have a search feature where the user can search for files (the code > > for that is already in place). > > > Now, I was thinking about having the search running in the background > > somehow, whilst the user can still navigate, create folders, copy, > > sort and do other stuffs normally. When the search finishes the user > > would get a notification and then could click on it and go to that > > activity (It ideally should be the same ListView I already use for > > browsing the files, I would just need to update the Adapter there with > > the latest processed data after clicking in the notification). > > > What's the best answer for that? Threading or AsyncTask? > > > Could anyone help me? > > > Cheers- Hide quoted text - > > - Show quoted text - -- 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.
