AsyncTask原理解析

1.概述

AsyncTask是一个轻量级的异步任务类,通常用于后台执行异步任务,并提供任务进度以便主线程更新ui的场景,AsyncTask内部维护了一个handler和两个线程池,handler用于主线程与线程池的切换,两个线程池分别用于任务排队和任务最终执行。

2.源码分析(api 28)

execute

AsyncTask开始执行任务是调用execute方法,所以我们从这个方法开始探究。

	@MainThread
    public final AsyncTask<Params, Progress, Result> execute(Params... params{
        return executeOnExecutor(sDefaultExecutor, params);
    }

	@MainThread
    public final AsyncTask<Params, Progress, Result> executeOnExecutor(Executor exec,
            Params... params) {
        if (mStatus != Status.PENDING) {
            switch (mStatus) {
                case RUNNING:
                    throw new IllegalStateException("Cannot execute task:"
                            + " the task is already running.");
                case FINISHED:
                    throw new IllegalStateException("Cannot execute task:"
                            + " the task has already been executed "
                            + "(a task can be executed only once)");
            }
        }

        mStatus = Status.RUNNING;

        onPreExecute();

        mWorker.mParams = params;
        exec.execute(mFuture);

        return this;
    }

我们看到execute实际上调用了executeOnExecutor方法,细心的同学会发这两个方法都注释着@MainThread,猜想此方法只能在主线程中调用,实际上确实是这样的,我们接下来会在源码中找到答案。继续看executeOnExecutor,首先会判断mStatus的状态,然后调用 onPreExecute() 方法做初始化工作,紧接着把我们的参数赋值给mWorker.mParams,最后执行sDefaultExecutor.execute()。大致流程就是这样,接下来我们要带着疑问继续探究sDefaultExecutor和mWorker。
我们找到mWorker初始化的构造方法:


	private final WorkerRunnable<Params, Result> mWorker;
    private final FutureTask<Result> mFuture;
	/**
     	* Creates a new asynchronous task. This constructor must be invoked on 		the UI thread.
     	*
     	* @hide
     */
    public AsyncTask(@Nullable Looper callbackLooper) {
        mHandler = callbackLooper == null || callbackLooper == Looper.getMainLooper()
            ? getMainHandler()
            : new Handler(callbackLooper);

        mWorker = new WorkerRunnable<Params, Result>() {
            public Result call() throws Exception {
                mTaskInvoked.set(true);
                Result result = null;
                try {
                    Process.setThreadPriority(Process.THREAD_PRIORITY_BACKGROUND);
                    //noinspection unchecked
                    result = doInBackground(mParams);
                    Binder.flushPendingCommands();
                } catch (Throwable tr) {
                    mCancelled.set(true);
                    throw tr;
                } finally {
                    postResult(result);
                }
                return result;
            }
        };

        mFuture = new FutureTask<Result>(mWorker) {
            @Override
            protected void done() {
                try {
                    postResultIfNotInvoked(get());
                } catch (InterruptedException e) {
                    android.util.Log.w(LOG_TAG, e);
                } catch (ExecutionException e) {
                    throw new RuntimeException("An error occurred while executing doInBackground()",
                            e.getCause());
                } catch (CancellationException e) {
                    postResultIfNotInvoked(null);
                }
            }
        };
    }

	private static abstract class WorkerRunnable<Params, Result> implements Callable<Result> {
        Params[] mParams;
    }

AsyncTask源码中有三个构造方法,最终都会调用到上面这个方法,我们看里面都做了什么,创建一个Callable类型的mWorker,然后把mWorker作为参数创建一个FutureTask类型的mFuture。没错流程就是这么简单,至于mWorker的run和mFuture的done我们暂时先不管,下面调用到的时候再具体分析。

接下来再看sDefaultExecutor是个何方神圣。

	private static volatile Executor sDefaultExecutor = SERIAL_EXECUTOR;
	public static final Executor SERIAL_EXECUTOR = new SerialExecutor();
	
	private static class SerialExecutor implements Executor {
        final ArrayDeque<Runnable> mTasks = new ArrayDeque<Runnable>();
        Runnable mActive;

        public synchronized void execute(final Runnable r) {
            mTasks.offer(new Runnable() {
                public void run() {
                    try {
                        r.run();
                    } finally {
                        scheduleNext();
                    }
                }
            });
            if (mActive == null) {
                scheduleNext();
            }
        }

        protected synchronized void scheduleNext() {
            if ((mActive = mTasks.poll()) != null) {
                THREAD_POOL_EXECUTOR.execute(mActive);
            }
        }
    }

sDefaultExecutor实际上是一个串行的线程池,mTasks是一个双向队列,可以看到execute被锁修饰,FutureTask会被一个接一个添加到mTasks中说明AsyncTask确实默认是串行执行,接着如果没有正在活动的task任务,即mActive==null,就执行THREAD_POOL_EXECUTOR.execute(mActive),当这个任务执行完毕后,就会取出下一个任务继续执行,知道任务全部执行。
我们再看THREAD_POOL_EXECUTOR.execute(mActive)这个方法,mActive就是我们传进来的mFuture,所以会调用mFuture.run()

public void run() {
        
        try {
            Callable<V> c = callable;
            if (c != null && state == NEW) {
                V result;
                boolean ran;
                try {
                    result = c.call();
                    ran = true;
                } catch (Throwable ex) {
                    result = null;
                    ran = false;
                    setException(ex);
                }
                if (ran)
                    set(result);
            }
        } finally {
          
        }
    }

result = c.call();这段代码又会调用mWorker.call()方法,所以我们最终执行了AsyncTask中mWorker的call()方法。由于futureTask的run方法是在线程池中执行的,所以mWorker的call方法也是在线程池中执行。思路已经捋清楚了,接下来就来看看具体怎么实现吧。

	mWorker = new WorkerRunnable<Params, Result>() {
            public Result call() throws Exception {
                mTaskInvoked.set(true);
                Result result = null;
                try {
                    Process.setThreadPriority(Process.THREAD_PRIORITY_BACKGROUND);
                    //noinspection unchecked
                    result = doInBackground(mParams);
                    Binder.flushPendingCommands();
                } catch (Throwable tr) {
                    mCancelled.set(true);
                    throw tr;
                } finally {
                    postResult(result);
                }
                return result;
            }
        };

首先会设置线程优先级,然后执行doInBackground(),是不是很熟悉,就是我们处理异步逻辑的地方,现在终于知道他是在线程池中执行的,最后调用了postResult(result)方法将任务结果发送出去。

	private Result postResult(Result result) {
        @SuppressWarnings("unchecked")
        Message message = getHandler().obtainMessage(MESSAGE_POST_RESULT,
                new AsyncTaskResult<Result>(this, result));
        message.sendToTarget();
        return result;
    }

	private static class InternalHandler extends Handler {
        public InternalHandler(Looper looper) {
            super(looper);
        }

        @SuppressWarnings({"unchecked", "RawUseOfParameterizedType"})
        @Override
        public void handleMessage(Message msg) {
            AsyncTaskResult<?> result = (AsyncTaskResult<?>) msg.obj;
            switch (msg.what) {
                case MESSAGE_POST_RESULT:
                    // There is only one result
                    result.mTask.finish(result.mData[0]);
                    break;
                case MESSAGE_POST_PROGRESS:
                    result.mTask.onProgressUpdate(result.mData);
                    break;
            }
        }
    }

将AsyncTask和执行结果result封装成标识为MESSAGE_POST_RESULT的Message通过InternalHandler发送到主线程。接着我们看finish()方法

	private void finish(Result result) {
        if (isCancelled()) {
            onCancelled(result);
        } else {
            onPostExecute(result);
        }
        mStatus = Status.FINISHED;
    }

在没有取消任务的情况下最终会调用到onPostExecute(),到这里AsyncTask的整个流程就分析完毕了,但仔细一想,我们好像还差一个**onProgressUpdate()**方法没看到,是的,由于我们没有调用publishProgress(),所以就不会发送MESSAGE_POST_PROGRESS,也就不会执行result.mTask.onProgressUpdate(result.mData)方法。

	@WorkerThread
    protected final void publishProgress(Progress... values) {
        if (!isCancelled()) {
            getHandler().obtainMessage(MESSAGE_POST_PROGRESS,
                    new AsyncTaskResult<Progress>(this, values)).sendToTarget();
        }
    }

总结

AsyncTask是由一个专门用来切换线程的handler和两个处理任务队列和任务执行的线程池构成的,且默认为串行执行,如果想并行执行,可以使用executeOnExecutor(AsyncTask.THREAD_POOL_EXECUTOR)来处理。

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值