1 背景
Android异步处理机制一直都是Android的一个核心,也是应用工程师面试的一个知识点。前面我们分析了Handler异步机制原理(不了解的可以阅读我的《Android异步消息处理机制详解及源码分析》文章),这里继续分析Android的另一个异步机制AsyncTask的原理。
当使用线程和Handler组合实现异步处理时,当每次执行耗时操作都创建一条新线程进行处理,性能开销会比较大。为了提高性能我们使用AsyncTask实现异步处理(其实也是线程和handler组合实现),因为其内部使用了java提供的线程池技术,有效的降低了线程创建数量及限定了同时运行的线程数,还有一些针对性的对池的优化操作。所以说AsyncTask是Android为我们提供的方便编写异步任务的工具类。
【工匠若水 http://blog.csdn.net/yanbober 转载烦请注明出处,尊重分享成果】
2 实例演示
先看下使用AsyncTask模拟下载的效果图:
看下代码,如下:
<code class="language-java hljs has-numbering"><span class="hljs-keyword">public</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">MainActivity</span> <span class="hljs-keyword">extends</span> <span class="hljs-title">Activity</span> {</span> <span class="hljs-annotation">@Override</span> <span class="hljs-keyword">protected</span> <span class="hljs-keyword">void</span> <span class="hljs-title">onCreate</span>(Bundle savedInstanceState) { <span class="hljs-keyword">super</span>.onCreate(savedInstanceState); setContentView(R.layout.activity_main); <span class="hljs-keyword">new</span> TestAsyncTask(<span class="hljs-keyword">this</span>).execute(); } <span class="hljs-keyword">static</span> <span class="hljs-keyword">final</span> class TestAsyncTask extends AsyncTask<Void, Integer, Boolean> { <span class="hljs-comment">//如上三个泛型参数从左到右含义依次为:</span> <span class="hljs-comment">//1. 在执行AsyncTask时需要传入的参数,可用于在后台任务中使用。</span> <span class="hljs-comment">//2. 后台任务执行时,如果需要在界面上显示当前的进度,则使用这个。</span> <span class="hljs-comment">//3. 当任务执行完毕后,如果需要对结果进行返回,则使用这个。</span> <span class="hljs-keyword">private</span> Context mContext = <span class="hljs-keyword">null</span>; <span class="hljs-keyword">private</span> ProgressDialog mDialog = <span class="hljs-keyword">null</span>; <span class="hljs-keyword">private</span> <span class="hljs-keyword">int</span> mCount = <span class="hljs-number">0</span>; <span class="hljs-keyword">public</span> <span class="hljs-title">TestAsyncTask</span>(Context context) { mContext = context; } <span class="hljs-comment">//在后台任务开始执行之间调用,用于进行一些界面上的初始化操作</span> <span class="hljs-keyword">protected</span> <span class="hljs-keyword">void</span> <span class="hljs-title">onPreExecute</span>() { <span class="hljs-keyword">super</span>.onPreExecute(); mDialog = <span class="hljs-keyword">new</span> ProgressDialog(mContext); mDialog.setMax(<span class="hljs-number">100</span>); mDialog.setProgressStyle(ProgressDialog.STYLE_HORIZONTAL); mDialog.show(); } <span class="hljs-comment">//这个方法中的所有代码都会在子线程中运行,我们应该在这里去处理所有的耗时任务</span> <span class="hljs-keyword">protected</span> Boolean <span class="hljs-title">doInBackground</span>(Void... params) { <span class="hljs-keyword">while</span> (mCount < <span class="hljs-number">100</span>) { publishProgress(mCount); mCount += <span class="hljs-number">20</span>; <span class="hljs-keyword">try</span> { Thread.sleep(<span class="hljs-number">1000</span>); } <span class="hljs-keyword">catch</span> (InterruptedException e) { e.printStackTrace(); } } <span class="hljs-keyword">return</span> <span class="hljs-keyword">true</span>; } <span class="hljs-comment">//当在后台任务中调用了publishProgress(Progress...)方法后,这个方法就很快会被调用</span> <span class="hljs-keyword">protected</span> <span class="hljs-keyword">void</span> <span class="hljs-title">onProgressUpdate</span>(Integer... values) { <span class="hljs-keyword">super</span>.onProgressUpdate(values); mDialog.setProgress(values[<span class="hljs-number">0</span>]); } <span class="hljs-comment">//当后台任务执行完毕并通过return语句进行返回时,这个方法就很快会被调用</span> <span class="hljs-keyword">protected</span> <span class="hljs-keyword">void</span> <span class="hljs-title">onPostExecute</span>(Boolean aBoolean) { <span class="hljs-keyword">super</span>.onPostExecute(aBoolean); <span class="hljs-keyword">if</span> (aBoolean && mDialog != <span class="hljs-keyword">null</span> && mDialog.isShowing()) { mDialog.dismiss(); } } } }</code><ul class="pre-numbering" style="display: block;"><li>1</li><li>2</li><li>3</li><li>4</li><li>5</li><li>6</li><li>7</li><li>8</li><li>9</li><li>10</li><li>11</li><li>12</li><li>13</li><li>14</li><li>15</li><li>16</li><li>17</li><li>18</li><li>19</li><li>20</li><li>21</li><li>22</li><li>23</li><li>24</li><li>25</li><li>26</li><li>27</li><li>28</li><li>29</li><li>30</li><li>31</li><li>32</li><li>33</li><li>34</li><li>35</li><li>36</li><li>37</li><li>38</li><li>39</li><li>40</li><li>41</li><li>42</li><li>43</li><li>44</li><li>45</li><li>46</li><li>47</li><li>48</li><li>49</li><li>50</li><li>51</li><li>52</li><li>53</li><li>54</li><li>55</li><li>56</li><li>57</li><li>58</li><li>59</li><li>60</li><li>61</li></ul>
可以看见Android帮我们封装好的AsyncTask还是很方便使用的,咱们不做过多说明。接下来直接分析源码。
【工匠若水 http://blog.csdn.net/yanbober 转载烦请注明出处,尊重分享成果】
3 Android5.1.1(API 22)AsyncTask源码分析
通过源码可以发现AsyncTask是一个抽象类,所以我们在在上面使用时需要实现它。
那怎么下手分析呢?很简单,我们就依据上面示例的流程来分析源码,具体如下。
3-1 AsyncTask实例化源码分析
<code class="language-java hljs has-numbering"> <span class="hljs-javadoc">/** * Creates a new asynchronous task. This constructor must be invoked on the UI thread. */</span> <span class="hljs-keyword">public</span> <span class="hljs-title">AsyncTask</span>() { mWorker = <span class="hljs-keyword">new</span> WorkerRunnable<Params, Result>() { <span class="hljs-keyword">public</span> Result <span class="hljs-title">call</span>() <span class="hljs-keyword">throws</span> Exception { mTaskInvoked.set(<span class="hljs-keyword">true</span>); Process.setThreadPriority(Process.THREAD_PRIORITY_BACKGROUND); <span class="hljs-comment">//noinspection unchecked</span> <span class="hljs-keyword">return</span> postResult(doInBackground(mParams)); } }; mFuture = <span class="hljs-keyword">new</span> FutureTask<Result>(mWorker) { <span class="hljs-annotation">@Override</span> <span class="hljs-keyword">protected</span> <span class="hljs-keyword">void</span> <span class="hljs-title">done</span>() { <span class="hljs-keyword">try</span> { postResultIfNotInvoked(get()); } <span class="hljs-keyword">catch</span> (InterruptedException e) { android.util.Log.w(LOG_TAG, e); } <span class="hljs-keyword">catch</span> (ExecutionException e) { <span class="hljs-keyword">throw</span> <span class="hljs-keyword">new</span> RuntimeException(<span class="hljs-string">"An error occured while executing doInBackground()"</span>, e.getCause()); } <span class="hljs-keyword">catch</span> (CancellationException e) { postResultIfNotInvoked(<span class="hljs-keyword">null</span>); } } }; }</code><ul class="pre-numbering" style="display: block;"><li>1</li><li>2</li><li>3</li><li>4</li><li>5</li><li>6</li><li>7</li><li>8</li><li>9</li><li>10</li><li>11</li><li>12</li><li>13</li><li>14</li><li>15</li><li>16</li><li>17</li><li>18</li><li>19</li><li>20</li><li>21</li><li>22</li><li>23</li><li>24</li><li>25</li><li>26</li><li>27</li><li>28</li><li>29</li><li>30</li></ul>
看见注释没有,AsyncTask的实例化只能在UI线程中。然后整个构造函数就只初始化了两个AsyncTask类的成员变量(mWorker和mFuture)。mWorker为匿名内部类的实例对象WorkerRunnable(实现了Callable接口),mFuture为匿名内部类的实例对象FutureTask,传入了mWorker作为形参(重写了FutureTask类的done方法)。
3-2 AsyncTask的execute方法源码分析
正如上面实例一样,得到AsyncTask实例化对象之后就执行了execute方法,所以看下execute方法的源码,如下:
<code class="language-java hljs has-numbering"> <span class="hljs-keyword">public</span> <span class="hljs-keyword">final</span> AsyncTask<Params, Progress, Result> <span class="hljs-title">execute</span>(Params... params) { <span class="hljs-keyword">return</span> executeOnExecutor(sDefaultExecutor, params); }</code><ul class="pre-numbering" style="display: block;"><li>1</li><li>2</li><li>3</li></ul>
可以看见,execute调运了executeOnExecutor方法,executeOnExecutor方法除过传入了params形参以外,还传入了一个static的SerialExecutor对象(SerialExecutor实现了Executor接口)。继续看下executeOnExecutor源码,如下:
<code class="language-java hljs has-numbering"> <span class="hljs-keyword">public</span> <span class="hljs-keyword">final</span> AsyncTask<Params, Progress, Result> <span class="hljs-title">executeOnExecutor</span>(Executor exec, Params... params) { <span class="hljs-keyword">if</span> (mStatus != Status.PENDING) { <span class="hljs-keyword">switch</span> (mStatus) { <span class="hljs-keyword">case</span> RUNNING: <span class="hljs-keyword">throw</span> <span class="hljs-keyword">new</span> IllegalStateException(<span class="hljs-string">"Cannot execute task:"</span> + <span class="hljs-string">" the task is already running."</span>); <span class="hljs-keyword">case</span> FINISHED: <span class="hljs-keyword">throw</span> <span class="hljs-keyword">new</span> IllegalStateException(<span class="hljs-string">"Cannot execute task:"</span> + <span class="hljs-string">" the task has already been executed "</span> + <span class="hljs-string">"(a task can be executed only once)"</span>); } } mStatus = Status.RUNNING; onPreExecute(); mWorker.mParams = params; exec.execute(mFuture); <span class="hljs-keyword">return</span> <span class="hljs-keyword">this</span>; }</code><ul class="pre-numbering" style="display: block;"><li>1</li><li>2</li><li>3</li><li>4</li><li>5</li><li>6</li><li>7</li><li>8</li><li>9</li><li>10</li><li>11</li><li>12</li><li>13</li><li>14</li><li>15</li><li>16</li><li>17</li><li>18</li><li>19</li><li>20</li><li>21</li><li>22</li><li>23</li></ul>
首先判断AsyncTask异步任务的状态,当处于RUNNING和FINISHED时就报IllegalStateException非法状态异常。由此可以看见一个AsyncTask的execute方法只能被调运一次。接着看见17行onPreExecute();没有?看下这个方法源码,如下:
<code class="language-java hljs has-numbering"> <span class="hljs-javadoc">/** * Runs on the UI thread before {@link #doInBackground}. * *<span class="hljs-javadoctag"> @see</span> #onPostExecute *<span class="hljs-javadoctag"> @see</span> #doInBackground */</span> <span class="hljs-keyword">protected</span> <span class="hljs-keyword">void</span> <span class="hljs-title">onPreExecute</span>() { }</code><ul class="pre-numbering" style="display: block;"><li>1</li><li>2</li><li>3</li><li>4</li><li>5</li><li>6</li><li>7</li><li>8</li></ul>
空方法,而且通过注释也能看见,这不就是我们AsyncTask中第一个执行的方法吗?是的。
回过头继续往下看,看见20行exec.execute(mFuture);代码没?exec就是形参出入的上面定义的static SerialExecutor对象(SerialExecutor实现了Executor接口),所以execute就是SerialExecutor静态内部类的方法喽,在执行execute方法时还传入了AsyncTask构造函数中实例化的第二个成员变量mFuture。我们来看下SerialExecutor静态内部类的代码,如下:
<code class="language-java hljs has-numbering"> <span class="hljs-keyword">private</span> <span class="hljs-keyword">static</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">SerialExecutor</span> <span class="hljs-keyword">implements</span> <span class="hljs-title">Executor</span> {</span> <span class="hljs-keyword">final</span> ArrayDeque<Runnable> mTasks = <span class="hljs-keyword">new</span> ArrayDeque<Runnable>(); Runnable mActive; <span class="hljs-keyword">public</span> <span class="hljs-keyword">synchronized</span> <span class="hljs-keyword">void</span> <span class="hljs-title">execute</span>(<span class="hljs-keyword">final</span> Runnable r) { mTasks.offer(<span class="hljs-keyword">new</span> Runnable() { <span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">run</span>() { <span class="hljs-keyword">try</span> { r.run(); } <span class="hljs-keyword">finally</span> { scheduleNext(); } } }); <span class="hljs-keyword">if</span> (mActive == <span class="hljs-keyword">null</span>) { scheduleNext(); } } <span class="hljs-keyword">protected</span> <span class="hljs-keyword">synchronized</span> <span class="hljs-keyword">void</span> <span class="hljs-title">scheduleNext</span>() { <span class="hljs-keyword">if</span> ((mActive = mTasks.poll()) != <span class="hljs-keyword">null</span>) { THREAD_POOL_EXECUTOR.execute(mActive); } } }</code><ul class="pre-numbering" style="display: block;"><li>1</li><li>2</li><li>3</li><li>4</li><li>5</li><li>6</li><li>7</li><li>8</li><li>9</li><li>10</li><li>11</li><li>12</li><li>13</li><li>14</li><li>15</li><li>16</li><li>17</li><li>18</li><li>19</li><li>20</li><li>21</li><li>22</li><li>23</li><li>24</li><li>25</li></ul>
在源码中可以看见,SerialExecutor在AsyncTask中是以常量的形式被使用的,所以在整个应用程序中的所有AsyncTask实例都会共用同一个SerialExecutor对象。
接着可以看见,SerialExecutor是使用ArrayDeque这个队列来管理Runnable对象的,如果我们一次性启动了很多个任务,首先在第一次运行execute()方法的时候会调用ArrayDeque的offer()方法将传入的Runnable对象添加到队列的最后,然后判断mActive对象是不是等于null,第一次运行是null,然后调用scheduleNext()方法,在这个方法中会从队列的头部取值,并赋值给mActive对象,然后调用THREAD_POOL_EXECUTOR去执行取出的取出的Runnable对象。之后如果再有新的任务被执行时就等待上一个任务执行完毕后才会得到执行,所以说同一时刻只会有一个线程正在执行,其余的均处于等待状态,这就是SerialExecutor类的核心作用。
我们再来看看上面用到的THREAD_POOL_EXECUTOR与execute,如下:
<code class="language-java hljs has-numbering"><span class="hljs-keyword">public</span> <span class="hljs-keyword">abstract</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">AsyncTask</span><<span class="hljs-title">Params</span>, <span class="hljs-title">Progress</span>, <span class="hljs-title">Result</span>> {</span> ...... <span class="hljs-keyword">private</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">final</span> <span class="hljs-keyword">int</span> CPU_COUNT = Runtime.getRuntime().availableProcessors(); <span class="hljs-keyword">private</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">final</span> <span class="hljs-keyword">int</span> CORE_POOL_SIZE = CPU_COUNT + <span class="hljs-number">1</span>; <span class="hljs-keyword">private</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">final</span> <span class="hljs-keyword">int</span> MAXIMUM_POOL_SIZE = CPU_COUNT * <span class="hljs-number">2</span> + <span class="hljs-number">1</span>; <span class="hljs-keyword">private</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">final</span> <span class="hljs-keyword">int</span> KEEP_ALIVE = <span class="hljs-number">1</span>; <span class="hljs-keyword">private</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">final</span> ThreadFactory sThreadFactory = <span class="hljs-keyword">new</span> ThreadFactory() { <span class="hljs-keyword">private</span> <span class="hljs-keyword">final</span> AtomicInteger mCount = <span class="hljs-keyword">new</span> AtomicInteger(<span class="hljs-number">1</span>); <span class="hljs-keyword">public</span> Thread <span class="hljs-title">newThread</span>(Runnable r) { <span class="hljs-keyword">return</span> <span class="hljs-keyword">new</span> Thread(r, <span class="hljs-string">"AsyncTask #"</span> + mCount.getAndIncrement()); } }; <span class="hljs-keyword">private</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">final</span> BlockingQueue<Runnable> sPoolWorkQueue = <span class="hljs-keyword">new</span> LinkedBlockingQueue<Runnable>(<span class="hljs-number">128</span>); <span class="hljs-javadoc">/** * An {@link Executor} that can be used to execute tasks in parallel. */</span> <span class="hljs-keyword">public</span> <span class="hljs-keyword">static</span> <span class="hljs-keyword">final</span> Executor THREAD_POOL_EXECUTOR = <span class="hljs-keyword">new</span> ThreadPoolExecutor(CORE_POOL_SIZE, MAXIMUM_POOL_SIZE, KEEP_ALIVE, TimeUnit.SECONDS, sPoolWorkQueue, sThreadFactory); ...... }</code><ul class="pre-numbering" style="display: block;"><li>1</li><li>2</li><li>3</li><li>4</li><li>5</li><li>6</li><li>7</li><li>8</li><li>9</li><li>10</li><li>11</li><li>12</li><li>13</li><li>14</li><li>15</li><li>16</li><li>17</li><li>18</li><li>19</li><li>20</li><li>21</li><li>22</li><li>23</li><li>24</li><li>25</li><li>26</li></ul>
看见没有,实质就是在一个线程池中执行,这个THREAD_POOL_EXECUTOR线程池是一个常量,也就是说整个App中不论有多少AsyncTask都只有这一个线程池。也就是说上面SerialExecutor类中execute()方法的所有逻辑就是在子线程中执行,注意SerialExecutor的execute方法有一个Runnable参数,这个参数就是mFuture对象,所以我们看下FutureTask类的run()方法,如下源码:
<code class="language-java hljs has-numbering"> <span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">run</span>() { <span class="hljs-keyword">if</span> (state != NEW || !UNSAFE.compareAndSwapObject(<span class="hljs-keyword">this</span>, runnerOffset, <span class="hljs-keyword">null</span>, Thread.currentThread())) <span class="hljs-keyword">return</span>; <span class="hljs-keyword">try</span> { Callable<V> c = callable; <span class="hljs-keyword">if</span> (c != <span class="hljs-keyword">null</span> && state == NEW) { V result; <span class="hljs-keyword">boolean</span> ran; <span class="hljs-keyword">try</span> { result = c.call(); ran = <span class="hljs-keyword">true</span>; } <span class="hljs-keyword">catch</span> (Throwable ex) { result = <span class="hljs-keyword">null</span>; ran = <span class="hljs-keyword">false</span>; setException(ex); } <span class="hljs-keyword">if</span> (ran) set(result); } } <span class="hljs-keyword">finally</span> { <span class="hljs-comment">// runner must be non-null until state is settled to</span> <span class="hljs-comment">// prevent concurrent calls to run()</span> runner = <span class="hljs-keyword">null</span>; <span class="hljs-comment">// state must be re-read after nulling runner to prevent</span> <span class="hljs-comment">// leaked interrupts</span> <span class="hljs-keyword">int</span> s = state; <span class="hljs-keyword">if</span> (s >= INTERRUPTING) handlePossibleCancellationInterrupt(s); } }</code><ul class="pre-numbering" style="display: block;"><li>1</li><li>2</li><li>3</li><li>4</li><li>5</li><li>6</li><li>7</li><li>8</li><li>9</li><li>10</li><li>11</li><li>12</li><li>13</li><li>14</li><li>15</li><li>16</li><li>17</li><li>18</li><li>19</li><li>20</li><li>21</li><li>22</li><li>23</li><li>24</li><li>25</li><li>26</li><li>27</li><li>28</li><li>29</li><li>30</li><li>31</li><li>32</li></ul>
看见没有?第7行的c = callable;其实就是AsyncTask构造函数中实例化FutureTask对象时传入的参数mWorker。12行看见result = c.call();
没有?其实就是调运WorkerRunnable类的call方法,所以我们回到AsyncTask构造函数的WorkerRunnable匿名内部内中可以看见如下:
<code class="language-java hljs has-numbering">mWorker = <span class="hljs-keyword">new</span> WorkerRunnable<Params, Result>() { <span class="hljs-keyword">public</span> Result <span class="hljs-title">call</span>() <span class="hljs-keyword">throws</span> Exception { mTaskInvoked.set(<span class="hljs-keyword">true</span>); Process.setThreadPriority(Process.THREAD_PRIORITY_BACKGROUND); <span class="hljs-comment">//noinspection unchecked</span> <span class="hljs-keyword">return</span> postResult(doInBackground(mParams)); } };</code><ul class="pre-numbering" style="display: block;"><li>1</li><li>2</li><li>3</li><li>4</li><li>5</li><li>6</li><li>7</li><li>8</li><li>9</li></ul>
看见没有?在postResult()方法的参数里面,我们可以看见doInBackground()方法。所以这验证了我们上面例子中使用的AsyncTask,首先在主线程执行onPreExecute方法,接着在子线程执行doInBackground方法,所以这也就是为什么我们可以在doInBackground()方法中去处理耗时操作的原因了,接着等待doInBackground方法耗时操作执行完毕以后将返回值传递给了postResult()方法。所以我们来看下postResult这个方法的源码,如下:
<code class="language-java hljs has-numbering"> <span class="hljs-keyword">private</span> Result <span class="hljs-title">postResult</span>(Result result) { <span class="hljs-annotation">@SuppressWarnings</span>(<span class="hljs-string">"unchecked"</span>) Message message = getHandler().obtainMessage(MESSAGE_POST_RESULT, <span class="hljs-keyword">new</span> AsyncTaskResult<Result>(<span class="hljs-keyword">this</span>, result)); message.sendToTarget(); <span class="hljs-keyword">return</span> result; }</code><ul class="pre-numbering" style="display: block;"><li>1</li><li>2</li><li>3</li><li>4</li><li>5</li><li>6</li><li>7</li></ul>
先看下这个getHandler拿到的是哪个Handler吧,如下:
<code class="language-java hljs has-numbering"> <span class="hljs-keyword">private</span> <span class="hljs-keyword">static</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">InternalHandler</span> <span class="hljs-keyword">extends</span> <span class="hljs-title">Handler</span> {</span> <span class="hljs-keyword">public</span> <span class="hljs-title">InternalHandler</span>() { <span class="hljs-keyword">super</span>(Looper.getMainLooper()); } <span class="hljs-annotation">@SuppressWarnings</span>({<span class="hljs-string">"unchecked"</span>, <span class="hljs-string">"RawUseOfParameterizedType"</span>}) <span class="hljs-annotation">@Override</span> <span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">handleMessage</span>(Message msg) { AsyncTaskResult<?> result = (AsyncTaskResult<?>) msg.obj; <span class="hljs-keyword">switch</span> (msg.what) { <span class="hljs-keyword">case</span> MESSAGE_POST_RESULT: <span class="hljs-comment">// There is only one result</span> result.mTask.finish(result.mData[<span class="hljs-number">0</span>]); <span class="hljs-keyword">break</span>; <span class="hljs-keyword">case</span> MESSAGE_POST_PROGRESS: result.mTask.onProgressUpdate(result.mData); <span class="hljs-keyword">break</span>; } } }</code><ul class="pre-numbering" style="display: block;"><li>1</li><li>2</li><li>3</li><li>4</li><li>5</li><li>6</li><li>7</li><li>8</li><li>9</li><li>10</li><li>11</li><li>12</li><li>13</li><li>14</li><li>15</li><li>16</li><li>17</li><li>18</li><li>19</li><li>20</li></ul>
看见没有,拿到的是MainLooper,也就是说在在UI线程中的Handler(不清楚的请阅读《Android异步消息处理机制详解及源码分析》文章)。所以上面的方法其实就是将子线程的数据发送到了UI来处理,也就是通过MESSAGE_POST_RESULT在handleMessage来处理。所以我们继续看handleMessage中的result.mTask.finish(result.mData[0]);就会发现finish的代码如下:
<code class="language-java hljs has-numbering"> <span class="hljs-keyword">private</span> <span class="hljs-keyword">void</span> <span class="hljs-title">finish</span>(Result result) { <span class="hljs-keyword">if</span> (isCancelled()) { onCancelled(result); } <span class="hljs-keyword">else</span> { onPostExecute(result); } mStatus = Status.FINISHED; }</code><ul class="pre-numbering" style="display: block;"><li>1</li><li>2</li><li>3</li><li>4</li><li>5</li><li>6</li><li>7</li><li>8</li></ul>
看见没有?依据返回值true与false回调AsyncTask的onPostExecute或者onCancelled方法。
到此是不是会好奇onProgressUpdate方法啥时候调运的呢?继续往下看可以发现handleMessage方法中的MESSAGE_POST_PROGRESS不就是回调我们UI Thread中的onProgressUpdate方法吗?那怎么样才能让他回调呢?追踪MESSAGE_POST_PROGRESS消息你会发现如下:
<code class="language-java hljs has-numbering"> <span class="hljs-keyword">protected</span> <span class="hljs-keyword">final</span> <span class="hljs-keyword">void</span> <span class="hljs-title">publishProgress</span>(Progress... values) { <span class="hljs-keyword">if</span> (!isCancelled()) { getHandler().obtainMessage(MESSAGE_POST_PROGRESS, <span class="hljs-keyword">new</span> AsyncTaskResult<Progress>(<span class="hljs-keyword">this</span>, values)).sendToTarget(); } }</code><ul class="pre-numbering" style="display: block;"><li>1</li><li>2</li><li>3</li><li>4</li><li>5</li><li>6</li></ul>
额,没意思了。这不就是我们上面例子中的在子线程的doInBackground耗时操作中调运通知回调onProgressUpdate的方法么。
看见没有,AsyncTask的实质就是Handler异步消息处理机制(不清楚的请阅读《Android异步消息处理机制详解及源码分析》文章),只是对线程做了优化处理和封装而已。
【工匠若水 http://blog.csdn.net/yanbober 转载烦请注明出处,尊重分享成果】
4 为当年低版本AsyncTask的臭名正身
接触Android比较久的可能都知道,在Android 3.0之前是并没有SerialExecutor这个类的(上面有分析)。那些版本的代码是直接创建了指定大小的线程池常量来执行task的。其中MAXIMUM_POOL_SIZE = 128;,所以那时候如果我们应用中一个界面需要同时创建的AsyncTask线程大于128(批量获取数据,譬如照片浏览瀑布流一次加载)程序直接就挂了。所以当时的AsyncTask因为这个原因臭名昭著。
回过头来看看现在高版本的AsyncTask,是不是没有这个问题了吧?因为现在是顺序执行的。而且更劲爆的是现在的AsyncTask还直接提供了客户化实现Executor接口功能,使用如下方法执行AsyncTask即可使用自定义Executor,如下:
<code class="language-java hljs has-numbering"> <span class="hljs-keyword">public</span> <span class="hljs-keyword">final</span> AsyncTask<Params, Progress, Result> <span class="hljs-title">executeOnExecutor</span>(Executor exec, Params... params) { ...... <span class="hljs-keyword">return</span> <span class="hljs-keyword">this</span>; }</code><ul class="pre-numbering" style="display: block;"><li>1</li><li>2</li><li>3</li><li>4</li><li>5</li></ul>
可以看出,在3.0以上版中AsyncTask已经不存在那个臭名昭著的Bug了,所以可以放心使用了,妈妈再也不用担心我的AsyncTask出Bug了。
【工匠若水 http://blog.csdn.net/yanbober 转载烦请注明出处,尊重分享成果】
5 AsyncTask与Handler异步机制对比
前面文章也分析过Handler了,这里也分析了AsyncTask,现在把他们两拽一起来比较比较。具体如下:
-
AsyncTask是对Handler与Thread的封装。
-
AsyncTask在代码上比Handler要轻量级别,但实际上比Handler更耗资源,因为AsyncTask底层是一个线程池,而Handler仅仅就是发送了一个消息队列。但是,如果异步任务的数据特别庞大,AsyncTask线程池比Handler节省开销,因为Handler需要不停的new Thread执行。
-
AsyncTask的实例化只能在主线程,Handler可以随意,只和Looper有关系。
6 AsyncTask总结
到此整个Android的AsyncTask已经分析完毕,相信你现在对于AsyncTask会有一个很深入的理解与认识了。
【工匠若水 http://blog.csdn.net/yanbober 转载烦请注明出处,尊重分享成果】