handle 首先想到的是和線程的關(guān)系癣防。

• 來看一下官方源碼花墩。

//ActivityThread中的main方法
   Looper.prepareMainLooper();

  // Find the value for {@link #PROC_START_SEQ_IDENT} if provided   on the command line.
  // It will be in the format "seq=114"
  long startSeq = 0;
  if (args != null) {
    for (int i = args.length - 1; i >= 0; --i)
  {
      if (args[i] != null &&args[i].startsWith(PROC_START_SEQ_IDENT)) {
           startSeq = Long.parseLong(
           args[i].substring(PROC_START_SEQ_IDENT.length()));
                  }
         }
  }
  ActivityThread thread = new ActivityThread();
  thread.attach(false, startSeq);
  if (sMainThreadHandler == null) {
          sMainThreadHandler = thread.getHandler();
  }
  if (false) 
  {
   Looper.myLooper().setMessageLogging(newLogPrinter(
          Log.DEBUG, "ActivityThread"));
  }

  // End of event ActivityThreadMain.
  Trace.traceEnd(Trace.TRACE_TAG_ACTIVITY_MANAGER);
  Looper.loop();

• 再來看一下Looper中的方法

/**
     * 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;
          ......
        for (;;) {
            Message msg = queue.next(); // might block
            if (msg == null) {
                // No message indicates that the message queue is quitting.
                return;
            }

           ......
           
            try {
                msg.target.dispatchMessage(msg);
                dispatchEnd = needEndTime ? SystemClock.uptimeMillis() : 0;
            } finally {
                if (traceTag != 0) {
                    Trace.traceEnd(traceTag);
                }
            }
           ......

            msg.recycleUnchecked();
        }
    }

里面起了個(gè)死循環(huán)不斷的重MessageQueue中取出Message,msg.target其實(shí)就是Handler翠订。

• 看一下prepareMainLooper()中干了什么事情峰伙？

    static final ThreadLocal<Looper> sThreadLocal = new ThreadLocal<Looper>();
    private static Looper sMainLooper;  // guarded by Looper.class

    final MessageQueue mQueue;
    final Thread mThread;

    public static void prepareMainLooper() {
        prepare(false);
        synchronized (Looper.class) {
            if (sMainLooper != null) {
                throw new IllegalStateException("The main Looper has already been prepared.");
            }
            sMainLooper = myLooper();
        }
    }
    public static void prepare() {
        prepare(true);
    }
    public static @Nullable Looper myLooper() {
        return sThreadLocal.get();
    }
    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));
    }

到這里我們很清楚了浸卦，是通過ThreadLocal綁定線程的缓醋。這里的ThreadLocal是一個(gè)鍵值對的結(jié)構(gòu)體如失。通過靜態(tài)的prepare方法保證線程安全，每個(gè)線程只能綁定一個(gè)Looper送粱。

• 再來看一下msg.target.dispatchMessage(msg)這個(gè)方法的源碼褪贵。

/**
     * Subclasses must implement this to receive messages.
     */
  public void handleMessage(Message msg) {
    }
    
    /**
     * 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);
        }
    }
  private static void handleCallback(Message message) {
        message.callback.run();
    }

這里很明顯看出dispatchMessage先調(diào)用msg中callback方法，其次調(diào)用Handler自己的Callback,最后調(diào)用handleMessage方法抗俄。