进程间通信--Handler的详解

版权声明:本文为博主原创文章,未经博主允许不得转载。 https://blog.csdn.net/qq348450134/article/details/48662881
1.首先new 一个handler,handler有两个关键的成员变量mLooper , mQueue
在初始化handler的时, hander会获取主线程的Looper,还有Looper中的MessageQueue记录起来。
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;
    }
2.当程序员去sendMessage的时候,会调用mqueue里面的queue.enqueueMessage(msg, uptimeMillis);方法将Message加入到消息队列中
同时,将message的target变量指向handler本身的对象。
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);

3.主线程遍历不停息的遍历消息队列messageQueue获取到Message对象,进而获取到Message对象中的target变量指向的对象,即Handler对象,再调用target中的dispatchMessage(Message msg)方法对消息进行处理。(ps:高级的死循环:for(;;))

Looper.class:
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();
}



 Handler.class:
public void dispatchMessage(Message msg) {
        if (msg.callback != null) {
            handleCallback(msg);
        } else {
            if (mCallback != null) {
                if (mCallback.handleMessage(msg)) {
                    return;
                }
            }
            handleMessage(msg);
        }
    }


展开阅读全文

没有更多推荐了,返回首页