Android Async Data Loading Methods
<p>If I need to asynchronously load some data via HTTP (or whatever) in order to update the UI, I have a few options when writing an Android application (among many others that I'm sure I missed):</p>

<ol>
<li><p>Use a regular thread and a handler to update the UI.</p></li>
<li><p><a href="http://developer.android.com/reference/android/os/AsyncTask.html" rel="nofollow">AsyncTask</a></p></li>
<li><p>Use and <a href="http://developer.android.com/reference/android/app/IntentService.html" rel="nofollow">IntentService</a>, and use either a callback or broadcast the results via an Intent.</p></li>
<li><p>Using <a href="http://developer.android.com/guide/topics/fundamentals/loaders.html" rel="nofollow">Loaders</a>.</p></li>
</ol>

<p>From what I understand, an IntentService is not tied to an Activity's lifecycle, so any changes to orientation, etc, will not impact the retrieval of data.  Where this is not the case for an AsyncTask or thread fired off within an Activity.</p>

<p>The reason for the question, is that I just recently read about <code>Loaders</code>, and am confused as to their application. They seem to be more closely tied to a data source, where if the data source changes, then "transparently" everything is handled appropriately. <code>Loaders</code> also appear to be tolerant to configuration/orientation changes (I believe).</p>

<p>I've been currently using an IntentService to make RESTful service calls, and broadcasting the results to be received by appropriate Activities.</p>

<p>I'm assuming I could write an HTTP based Loader, but I'm not sure if this is the best use of this mechanism.</p>

<p>What are the advantages/disadvantages to using one of the async data loading methods over any other?     </p>
