android中消息机制

一，MessageQueue
消息队列故名思意是用来存储消息的，不过它不是队列，是链表，消息队列有两个操作，一个是入队操作enqueueMessage(),另一个是读取操作next(),入队操作是往消息队列中插入一条消息，读取消息是从消息队列中取出一条消息并将其从消息对列中移除。

二，Looper
在消息机制中扮演着消息循环的角色，具体来说就是它不停的从MessageQueue中查看是否有新消息，如果有新消息就立即处理，
Looper.prepare()为当前线程创建一个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));
    }

private Looper(boolean quitAllowed){
            mQueue = new MessageQueue(quitAllowed);
            mThread = Thread.currentThread();
        }

所以在Looper.prepare()为当前线程创建了Looper和MessageQueue;

Looper.loop()该方法是一个死循环，它会调用MessageQueue的next()方法来在消息队列中查找新的消息，如果有新的消息会调用Handler的dispatchMessage(msg)方法，该方法中调用handlerMessage方法，交给handler来处理，源码中msg.target是发送这条消息的Handler对象

 /**
     * 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.recycle();
        }
    }

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);
        }
    }

三，Handler
Handler有一系列的sendMessage方法，不过最终都是调用sendMessageAtTime方法

源码

 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);
    }

最后将消息发从消息队列中入队
再看一下sendEmptyMessage

 public final boolean sendEmptyMessage(int what)
    {
        return sendEmptyMessageDelayed(what, 0);
    }

 public final boolean sendEmptyMessageDelayed(int what, long delayMillis) {
        Message msg = Message.obtain();
        msg.what = what;
        return sendMessageDelayed(msg, delayMillis);
    }

sendEmptyMessage表示发送空的消息，即Message里面没有数据

我们在调用Handler的默认构造方法public Handler()创建handler的时候，它会调用public Handler(Callback callback, boolean async)

 /**
     * Default constructor associates this handler with the {@link Looper} for the
     * current thread.
     *
     * If this thread does not have a looper, this handler won't be able to receive messages
     * so an exception is thrown.
     */
    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());
            }
        }

        //获取当前线程的Looper
        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对象会抛出异常”Can’t create handler inside thread that has not called Looper.prepare()”

总结：具体的流程是：handler发送一条新的消息，然后这个消息会进入消息队列，这个过程是有handler完成的，此时，Looper一直在循环查找消息队列中是否有新的消息，此刻发现来了新的消息，就调用MessageQueue的next()方法将消息取出来，并将其从消息队列中移除，然后在Looper的loop()中调用handler的dipatchMessage方法将消息交给handler的handleMessage()方法去处理