異步消息處理流程的示意圖如下圖所示：
（一）Handler的常規使用方式
public class MainActivity extends AppCompatActivity {
public static final String TAG = MainActivity.class.getSimpleName();
private TextView texttitle = null;
/**
* 在主線程中定義Handler，並實現對應的handleMessage方法
*/
public static Handler mHandler = new Handler() {
@Override
public void handleMessage(Message msg) {
if (msg.what == 101) {
Log.i(TAG, "接收到handler消息...");
}
}
};
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
texttitle = (TextView) findViewById(R.id.texttitle);
texttitle.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {
new Thread() {
@Override
public void run() {
// 在子線程中發送異步消息
mHandler.sendEmptyMessage(101);
}
}.start();
}
});
}
}
可以看出，一般handler的使用方式都是在主線程中定義Handler，然後在子線程中調用mHandler.sendEmptyMessage();方法，然麼這裏有一個疑問了，我們可以在子線程中定義Handler麼？
（二）如何在子線程中定義Handler？
我們在子線程中定義Handler，看看結果:
texttitle.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {
new Thread() {
@Override
public void run() {
Handler mHandler = new Handler() {
@Override
public void handleMessage(Message msg) {
if (msg.what == 101) {
Log.i(TAG, "在子線程中定義Handler，並接收到消息。。。");
}
}
};
}
}.start();
}
});
點擊按鈕並運行這段代碼：
可以看出來在子線程中定義Handler對象出錯了，難道Handler對象的定義或者是初始化只能在主線程中？ 其實不是這樣的，錯誤信息中提示的已經很明顯了，在初始化Handler對象之前需要調用Looper.prepare()方法，那麼好了，我們添加這句代碼再次執行一次：
texttitle.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {
new Thread() {
@Override
public void run() {
Looper.prepare();
Handler mHandler = new Handler() {
@Override
public void handleMessage(Message msg) {
if (msg.what == 101) {
Log.i(TAG, "在子線程中定義Handler，並接收到消息。。。");
}
}
};
}
}.start();
}
});
再次點擊按鈕執行該段代碼之後，程序已經不會報錯了，那麼這說明初始化Handler對象的時候我們是需要調用Looper.prepare()的，那麼主線程中爲什麼可以直接初始化Handler呢？
其實不是這樣的，在App初始化的時候會執行ActivityThread的main方法：
public static void main(String[] args) {
Trace.traceBegin(Trace.TRACE_TAG_ACTIVITY_MANAGER, "ActivityThreadMain");
SamplingProfilerIntegration.start();
// CloseGuard defaults to true and can be quite spammy. We
// disable it here, but selectively enable it later (via
// StrictMode) on debug builds, but using DropBox, not logs.
CloseGuard.setEnabled(false);
Environment.initForCurrentUser();
// Set the reporter for event logging in libcore
EventLogger.setReporter(new EventLoggingReporter());
AndroidKeyStoreProvider.install();
// Make sure TrustedCertificateStore looks in the right place for CA certificates
final File configDir = Environment.getUserConfigDirectory(UserHandle.myUserId());
TrustedCertificateStore.setDefaultUserDirectory(configDir);
Process.setArgV0("<pre-initialized>");
Looper.prepareMainLooper();
ActivityThread thread = new ActivityThread();
thread.attach(false);
if (sMainThreadHandler == null) {
sMainThreadHandler = thread.getHandler();
}
if (false) {
Looper.myLooper().setMessageLogging(new
LogPrinter(Log.DEBUG, "ActivityThread"));
}
// End of event ActivityThreadMain.
Trace.traceEnd(Trace.TRACE_TAG_ACTIVITY_MANAGER);
Looper.loop();
throw new RuntimeException("Main thread loop unexpectedly exited");
}
可以看到原來Looper.prepare()方法在這裏調用了，所以在其他地方我們就可以直接初始化Handler了。
並且我們可以看到還調用了：Looper.loop()方法，通過參考閱讀其他文章我們可以知道一個Handler的標準寫法其實是這樣的：
Looper.prepare();
Handler mHandler = new Handler() {
@Override
public void handleMessage(Message msg) {
if (msg.what == 101) {
Log.i(TAG, "在子線程中定義Handler，並接收到消息。。。");
}
}
};
Looper.loop();
（三）查看Handler源碼
1、查看Looper.prepare()方法
// sThreadLocal.get() will return null unless you've called prepare().
static final ThreadLocal<Looper> sThreadLocal = new ThreadLocal<Looper>();
/** Initialize the current thread as a looper.
* This gives you a chance to create handlers that then reference
* this looper, before actually starting the loop. Be sure to call
* {@link #loop()} after calling this method, and end it by calling
* {@link #quit()}.
*/
public static void prepare() {
prepare(true);
}
private static void prepare(boolean quitAllowed) {
if (sThreadLocal.get() != null) {
throw new RuntimeException("Only one Looper may be created per thread");
}
sThreadLocal.set(new Looper(quitAllowed));
}
可以看到Looper中有一個ThreadLocal成員變量，熟悉JDK的同學應該知道，當使用ThreadLocal維護變量時，ThreadLocal爲每個使用該變量的線程提供獨立的變量副本，所以每一個線程都可以獨立地改變自己的副本，而不會影響其它線程所對應的副本。具體參考：徹底理解ThreadLocal 由此可以看出在每個線程中Looper.prepare()能且只能調用一次，這裏我們可以嘗試一下調用兩次的情況。
/**
* 這裏Looper.prepare()方法調用了兩次
*/
Looper.prepare();
Looper.prepare();
Handler mHandler = new Handler() {
@Override
public void handleMessage(Message msg) {
if (msg.what == 101) {
Log.i(TAG, "在子線程中定義Handler，並接收到消息。。。");
}
}
};
Looper.loop();
再次運行程序，點擊按鈕，執行該段代碼：
可以看到程序出錯，並提示prepare中的Excetion信息。
我們繼續看Looper對象的構造方法，可以看到在其構造方法中初始化了一個MessageQueue對象：
private Looper(boolean quitAllowed) {
mQueue = new MessageQueue(quitAllowed);
mThread = Thread.currentThread();
}
綜上小結（1）：Looper.prepare()方法初始話了一個Looper對象並關聯在一個MessageQueue對象，並且一個線程中只有一個Looper對象，只有一個MessageQueue對象。
2、查看Handler對象的構造方法
public Handler(Callback callback, boolean async) {
if (FIND_POTENTIAL_LEAKS) {
final Class<? extends Handler> klass = getClass();
if ((klass.isAnonymousClass() || klass.isMemberClass() || klass.isLocalClass()) &&
(klass.getModifiers() & Modifier.STATIC) == 0) {
Log.w(TAG, "The following Handler class should be static or leaks might occur: " +
klass.getCanonicalName());
}
}
mLooper = Looper.myLooper();
if (mLooper == null) {
throw new RuntimeException(
"Can't create handler inside thread that has not called Looper.prepare()");
}
mQueue = mLooper.mQueue;
mCallback = callback;
mAsynchronous = async;
}
可以看出在Handler的構造方法中，主要初始化了一下變量，並判斷Handler對象的初始化不應再內部類，靜態類，匿名類中，並且保存了當前線程中的Looper對象。
綜上小結（2）：Looper.prepare()方法初始話了一個Looper對象並關聯在一個MessageQueue對象，並且一個線程中只有一個Looper對象，只有一個MessageQueue對象。而Handler的構造方法則在Handler內部維護了當前線程的Looper對象
3、查看handler.sendMessage(msg)方法 一般的，我們發送異步消息的時候會這樣調用：
mHandler.sendMessage(new Message());
通過不斷的跟進源代碼，其最後會調用：
private boolean enqueueMessage(MessageQueue queue, Message msg, long uptimeMillis) {
msg.target = this;
if (mAsynchronous) {
msg.setAsynchronous(true);
}
return queue.enqueueMessage(msg, uptimeMillis);
}
原來msg.target就是Handler對象本身；而這裏的queue對象就是我們的Handler內部維護的Looper對象關聯的MessageQueue對象。查看messagequeue對象的enqueueMessage方法：
boolean enqueueMessage(Message msg, long when) {
if (msg.target == null) {
throw new IllegalArgumentException("Message must have a target.");
}
if (msg.isInUse()) {
throw new IllegalStateException(msg + " This message is already in use.");
}
synchronized (this) {
if (mQuitting) {
IllegalStateException e = new IllegalStateException(
msg.target + " sending message to a Handler on a dead thread");
Log.w(TAG, e.getMessage(), e);
msg.recycle();
return false;
}
msg.markInUse();
msg.when = when;
Message p = mMessages;
boolean needWake;
if (p == null || when == 0 || when < p.when) {
// New head, wake up the event queue if blocked.
msg.next = p;
mMessages = msg;
needWake = mBlocked;
} else {
// Inserted within the middle of the queue. Usually we don't have to wake
// up the event queue unless there is a barrier at the head of the queue
// and the message is the earliest asynchronous message in the queue.
needWake = mBlocked && p.target == null && msg.isAsynchronous();
Message prev;
for (;;) {
prev = p;
p = p.next;
if (p == null || when < p.when) {
break;
}
if (needWake && p.isAsynchronous()) {
needWake = false;
}
}
msg.next = p; // invariant: p == prev.next
prev.next = msg;
}
// We can assume mPtr != 0 because mQuitting is false.
if (needWake) {
nativeWake(mPtr);
}
}
return true;
}
可以看到這裏MessageQueue並沒有使用列表將所有的Message保存起來，而是使用Message.next保存下一個Message，從而按照時間將所有的Message排序；
4、查看Looper.Loop()方法
/**
* Run the message queue in this thread. Be sure to call
* {@link #quit()} to end the loop.
*/
public static void loop() {
final Looper me = myLooper();
if (me == null) {
throw new RuntimeException("No Looper; Looper.prepare() wasn't called on this thread.");
}
final MessageQueue queue = me.mQueue;
// Make sure the identity of this thread is that of the local process,
// and keep track of what that identity token actually is.
Binder.clearCallingIdentity();
final long ident = Binder.clearCallingIdentity();
for (;;) {
Message msg = queue.next(); // might block
if (msg == null) {
// No message indicates that the message queue is quitting.
return;
}
// This must be in a local variable, in case a UI event sets the logger
Printer logging = me.mLogging;
if (logging != null) {
logging.println(">>>>> Dispatching to " + msg.target + " " +
msg.callback + ": " + msg.what);
}
msg.target.dispatchMessage(msg);
if (logging != null) {
logging.println("<<<<< Finished to " + msg.target + " " + msg.callback);
}
// Make sure that during the course of dispatching the
// identity of the thread wasn't corrupted.
final long newIdent = Binder.clearCallingIdentity();
if (ident != newIdent) {
Log.wtf(TAG, "Thread identity changed from 0x"
+ Long.toHexString(ident) + " to 0x"
+ Long.toHexString(newIdent) + " while dispatching to "
+ msg.target.getClass().getName() + " "
+ msg.callback + " what=" + msg.what);
}
msg.recycleUnchecked();
}
}
可以看到方法的內容還是比較多的。可以看到Looper.loop()方法裏起了一個死循環，不斷的判斷MessageQueue中的消息是否爲空，如果爲空則直接return掉，然後執行queue.next()方法：
Message next() {
// Return here if the message loop has already quit and been disposed.
// This can happen if the application tries to restart a looper after quit
// which is not supported.
final long ptr = mPtr;
if (ptr == 0) {
return null;
}
int pendingIdleHandlerCount = -1; // -1 only during first iteration
int nextPollTimeoutMillis = 0;
for (;;) {
if (nextPollTimeoutMillis != 0) {
Binder.flushPendingCommands();
}
nativePollOnce(ptr, nextPollTimeoutMillis);
synchronized (this) {
// Try to retrieve the next message. Return if found.
final long now = SystemClock.uptimeMillis();
Message prevMsg = null;
Message msg = mMessages;
if (msg != null && msg.target == null) {
// Stalled by a barrier. Find the next asynchronous message in the queue.
do {
prevMsg = msg;
msg = msg.next;
} while (msg != null && !msg.isAsynchronous());
}
if (msg != null) {
if (now < msg.when) {
// Next message is not ready. Set a timeout to wake up when it is ready.
nextPollTimeoutMillis = (int) Math.min(msg.when - now, Integer.MAX_VALUE);
} else {
// Got a message.
mBlocked = false;
if (prevMsg != null) {
prevMsg.next = msg.next;
} else {
mMessages = msg.next;
}
msg.next = null;
if (DEBUG) Log.v(TAG, "Returning message: " + msg);
msg.markInUse();
return msg;
}
} else {
// No more messages.
nextPollTimeoutMillis = -1;
}
// Process the quit message now that all pending messages have been handled.
if (mQuitting) {
dispose();
return null;
}
// If first time idle, then get the number of idlers to run.
// Idle handles only run if the queue is empty or if the first message
// in the queue (possibly a barrier) is due to be handled in the future.
if (pendingIdleHandlerCount < 0
&& (mMessages == null || now < mMessages.when)) {
pendingIdleHandlerCount = mIdleHandlers.size();
}
if (pendingIdleHandlerCount <= 0) {
// No idle handlers to run. Loop and wait some more.
mBlocked = true;
continue;
}
if (mPendingIdleHandlers == null) {
mPendingIdleHandlers = new IdleHandler[Math.max(pendingIdleHandlerCount, 4)];
}
mPendingIdleHandlers = mIdleHandlers.toArray(mPendingIdleHandlers);
}
// Run the idle handlers.
// We only ever reach this code block during the first iteration.
for (int i = 0; i < pendingIdleHandlerCount; i++) {
final IdleHandler idler = mPendingIdleHandlers[i];
mPendingIdleHandlers[i] = null; // release the reference to the handler
boolean keep = false;
try {
keep = idler.queueIdle();
} catch (Throwable t) {
Log.wtf(TAG, "IdleHandler threw exception", t);
}
if (!keep) {
synchronized (this) {
mIdleHandlers.remove(idler);
}
}
}
// Reset the idle handler count to 0 so we do not run them again.
pendingIdleHandlerCount = 0;
// While calling an idle handler, a new message could have been delivered
// so go back and look again for a pending message without waiting.
nextPollTimeoutMillis = 0;
}
}
可以看到其大概的實現邏輯就是Message的出棧操作，裏面可能對線程，併發控制做了一些限制等。獲取到棧頂的Message對象之後開始執行：
msg.target.dispatchMessage(msg);
那麼msg.target是什麼呢？通過追蹤可以知道就是我們定義的Handler對象，然後我們查看一下Handler類的dispatchMessage方法：
/**
* Handle system messages here.
*/
public void dispatchMessage(Message msg) {
if (msg.callback != null) {
handleCallback(msg);
} else {
if (mCallback != null) {
if (mCallback.handleMessage(msg)) {
return;
}
}
handleMessage(msg);
}
}
可以看到，如果我們設置了callback（Runnable對象）的話，則會直接調用handleCallback方法：
private static void handleCallback(Message message) {
message.callback.run();
}
即，如果我們在初始化Handler的時候設置了callback（Runnable）對象，則直接調用run方法。比如我們經常寫的runOnUiThread方法：
runOnUiThread(new Runnable() {
@Override
public void run() {
}
});
看其內部實現：
public final void runOnUiThread(Runnable action) {
if (Thread.currentThread() != mUiThread) {
mHandler.post(action);
} else {
action.run();
}
}
而如果msg.callback爲空的話，會直接調用我們的mCallback.handleMessage(msg)，即handler的handlerMessage方法。由於Handler對象是在主線程中創建的，所以handler的handlerMessage方法的執行也會在主線程中。
綜上可以知道：
1）主線程中定義Handler，直接執行：
Handler mHandler = new Handler() {
@Override
public void handleMessage(Message msg) {
super.handleMessage(msg);
}
};
而如果想要在子線程中定義Handler，則標準的寫法爲：
// 初始化該線程Looper，MessageQueue，執行且只能執行一次
Looper.prepare();
// 初始化Handler對象，內部關聯Looper對象
Handler mHandler = new Handler() {
@Override
public void handleMessage(Message msg) {
super.handleMessage(msg);
}
};
// 啓動消息隊列出棧死循環
Looper.loop();
2）一個線程中只存在一個Looper對象，只存在一個MessageQueue對象，可以存在N個Handler對象，Handler對象內部關聯了本線程中唯一的Looper對象，Looper對象內部關聯着唯一的一個MessageQueue對象。
3）MessageQueue消息隊列不是通過列表保存消息（Message）列表的，而是通過Message對象的next屬性關聯下一個Message從而實現列表的功能，同時所有的消息都是按時間排序的。
4）android中兩個子線程相互交互同樣可以通過Handler的異步消息機制實現，可以在線程a中定義Handler對象，而在線程b中獲取handler的引用並調用sendMessage方法。
5）activity內部默認存在一個handler的成員變量，android中一些其他的異步消息機制的實現方法： Handler的post方法：
mHandler.post(new Runnable() {
@Override
public void run() {
}
});
查看其內部實現：
public final boolean post(Runnable r)
{
return sendMessageDelayed(getPostMessage(r), 0);
}
可以發現其內部調用就是sendMessage系列方法。。。
view的post方法：
public boolean post(Runnable action) {
final AttachInfo attachInfo = mAttachInfo;
if (attachInfo != null) {
return attachInfo.mHandler.post(action);
}
// Assume that post will succeed later
ViewRootImpl.getRunQueue().post(action);
return true;
}
可以發現其調用的就是activity中默認保存的handler對象的post方法。
activity的runOnUiThread方法：
public final void runOnUiThread(Runnable action) {
if (Thread.currentThread() != mUiThread) {
mHandler.post(action);
} else {
action.run();
}
}
判斷當前線程是否是UI線程，如果不是，則調用handler的post方法，否則直接執行run方法
