1.什么是Android的消息机制
提到Android的消息机制大家应该都不会陌生，在日常的开发中不可避免的要涉及到这方面的内容。在开发的角度上来看，Android的消息机制主要是指Handler的运行机制，Handler在运行的过程中需要底层的MessageQueue和Looper的支持，MessageQueue为消息队列，但是它的内部储存结构并不是队列而是链表的结构，毕竟对于MessageQueue这种要频繁的进行插入和删除操作的结构来说，使用链表会有一定的优势，而Looper中文翻译为循环，在这里可以理解为消息的循环。由于MessageQueue只是一个消息的储存单元，而不能去处理消息，Looper的出现就正好填补了这个空缺，在消息机制的工作过程中Looper会以无限循环的形式去在MessageQueue中查找是否有新的消息，如果有新的消息就把它交给Handler去处理，如果没有新的消息就阻塞。总之Handler、MessageQueue和Looper的三者关系可以概括为，Looper中维护着一个MessageQueue， Handler发送的消息会进入到MessageQueue也就是消息队列中，同时Looper会不断的轮询MessageQueue中是否有消息，如果存在消息，Looper将消息从MessageQueue中取出，交给Handler处理。
以上就是Android消息机制的原理图
2.MessageQueue的工作原理
在MessageQueue中最重要的两个操作就是插入和读取，这两个操作分别对应的方法为enqueueMessage和next，其中enqueueMessage的作用就是往消息队列中插入一条消息，而next的作用则是从消息队列中读取出一条消息并将其从消息队列中移除。
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;
}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;
}
}从next的源代码中可以看出，在next()方法中启动一个无限循环，如果消息队列中有消息时，next()方法会返回这条消息并且将这条消息从MessageQueue中删除，如果消息队列中没有消息，那么next()方法将会一直阻塞在这里。
3.Looper的工作原理
Looper在Android的消息机制中扮演着消息循环的角色，具体来说它会不停的从MessageQueue中查看是否有新的消息，如果有新的消息就传递给Handler进行处理，否则就会一直阻塞在那里。我们都知道Handler的工作需要Looper，在没有Looper的线程中使用Handler就会报错，其实可以通过Looper.prepare()为当前线程创建一个Looper，紧接着通过Looper.loop()方法来开启消息队列的循环。
Looper.prepare()的源码如下
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构造方法的源码如下
private Looper(boolean quitAllowed){
mQueue = new MessageQueue(quitAllowed);
mThread = Thread.currentThread();
}Looper.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();
}
} 由上文对MessageQueue的介绍中可以知道，如果消息列表中没有消息，next()方法则会阻塞，因此loop()方法当消息列表中没有消息时是处于阻塞状态。当Looper的quit方法被调用时，Looper就会调用MessageQueue的quit或者quitSafely方法来通知消息队列的退出，当消息队列被标记为退出状态时，它的next()方法就会返回null。
4.Handler的工作原理
Handler的工作主要包含消息的发送和接收过程，消息的发送主要是通过post的一系列方法和send一系列方法来实现，而post的一系列方法最终也是通过send的一系列方法来实现的，消息的接收是通过在主线程中创建Handler对象并重写handleMessage()方法，在该方法中接收并处理消息。
创建Handler对象并重写handleMessage()方法
Handler mHandler = new Handler(){
@Override
public void handleMessage(Message msg) {
// TODO Auto-generated method stub
super.handleMessage(msg);
}
};mHandler.sendMessage(msg)；
public Handler() {
this(null, false);
}
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;
}Looper.myLooper()的源码如下
public static @Nullable Looper myLooper() {
return sThreadLocal.get();
}sendMessage()的源码如下
public final boolean sendMessage(Message msg)
{
return sendMessageDelayed(msg, 0);
}
public final boolean sendMessageDelayed(Message msg, long delayMillis)
{
if (delayMillis < 0) {
delayMillis = 0;
}
return sendMessageAtTime(msg, SystemClock.uptimeMillis() + delayMillis);
}
public boolean sendMessageAtTime(Message msg, long uptimeMillis) {
MessageQueue queue = mQueue;
if (queue == null) {
RuntimeException e = new RuntimeException(
this + " sendMessageAtTime() called with no mQueue");
Log.w("Looper", e.getMessage(), e);
return false;
}
return enqueueMessage(queue, msg, uptimeMillis);
}
private boolean enqueueMessage(MessageQueue queue, Message msg, long uptimeMillis) {
msg.target = this;
if (mAsynchronous) {
msg.setAsynchronous(true);
}
return queue.enqueueMessage(msg, uptimeMillis);
} dispatchMessage()的源码如下
public void dispatchMessage(Message msg) {
if (msg.callback != null) {
handleCallback(msg);
} else {
if (mCallback != null) {
if (mCallback.handleMessage(msg)) {
return;
}
}
handleMessage(msg);
}
}
private static void handleCallback(Message message) {
message.callback.run();
}
public void handleMessage(Message msg) {
}5.总结
Handler会通过以下三步实现跨线程通信
- 系统在主线程ActivityThread中已经调用Looper.prepareMainLooper()创建主线程的Looper，并调用Looper.loop()启动轮询，不断地通过MessageQueue的next()方法从消息列表中取出消息，当没有消息是，next()处于阻塞状态，Looper.loop()也处于阻塞状态
- 当我们在Activity等运行在主线程的组件中创建Handler时，Handler通过Looper.myLooper()获取与当前线程也就是主线程关联的Looper对象，同时Handler也持有了Looper中的MessageQueue
- 子线程持有主线程创建的Handler对象，在子线程中通过Handler的send()或post()的系列方法发送消息，send()与post()的系列方法最终都是通过Handler持有的MessageQueue对象调用enqueueMessage方法将消息插入队列,触发在主线程主线程中轮询的Looper用过loop()取出消息，并在loop()中调用Handler的dispatchMessage()方法，将消息交由Handler处理，最终达到了子线程进行IO操作后发送消息，主线程做相应的消息处理
185
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
