The documentation indicates that AsyncQueryHandler is for use with ContentResolver and, therefore, content providers. If that is your use case, and it is working, there is probably no reason to consider changing.
AsyncTask is an independent construct and is used for performing background operations in general, not just with content providers. On Tue, Nov 23, 2010 at 2:26 PM, BigEHokie <[email protected]> wrote: > Can anyone tell me when I should use one over the other? In my app, I > currently use AsyncQueryHandler and make updates to the UI in the > onQueryComplete() callback and I'm not under the impression this is > not a good thing. > > However, looking at the documentation, I'm unsure when I would use the > AsyncQueryHandler over the AsyncTask. > > Thanks in advance. > > -- > 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 > -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Warescription: Three Android Books, Plus Updates, One Low Price! -- 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
