Android   发布时间:2022-04-28  发布网站:大佬教程  code.js-code.com
大佬教程收集整理的这篇文章主要介绍了Android Handler消息派发机制源码分析大佬教程大佬觉得挺不错的,现在分享给大家,也给大家做个参考。

注:这里只是说一下sendmessage的一个过程,post就类似的
如果我们需要发送消息,会调用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);
}

接下来设定延迟时间,然后继续调用sendmessageAtTime方法 

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

这里获得了消息队列,检查队列是否存在,然后返回enquemessage的方法的执行结果,这个结果是说明消息能否进入队列的一个布尔值 

private Boolean enqueuemessage(messageQueue queue,message msg,long uptimeMillis) {
 msg.target = this;
 if (mAsynchronous) {
  msg.setAsynchronous(true);
 }
 return queue.enqueuemessage(msg,uptimeMillis);
}

这里是对消息进行入队处理,下面就是在messageQueue中对消息进行入队 

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);
   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
   // @R_616_6296@e 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;
}

就是对传递过来的消息进行一些封装然后放到队列中,至此我们的sendmessage处理完毕,返回的结果是进队是否成功的布尔值,那么究竟消息之后是如何被处理的呢?
我们可以看到在Handler构造的时候记录了一个Looper对象,也记录了一个回掉函数 

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

这里的myLooper方法返回的是当前线程关联的一个Looper对象

 public static @Nullable Looper myLooper() {
 return sThreadLocal.get();
} 

当Looper实例化了以后会执行自己的prepare方法后执行loop方法,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();
 }
}

在循环中如果读取到了消息,就会执行dispatchmessage方法,然后分派完消息之后再执行一次recycleUnchecked方法来重用这个message,我们看到dispatchmessage方法 

public void dispatchmessage(message msg) {
 if (msg.callBACk != null) {
  handleCallBACk(msg);
 } else {
  if (mCallBACk != null) {
   if (mCallBACk.handlemessage(msg)) {
    return;
   }
  }
  handlemessage(msg);
 }
}

这里看到直接执行了一个handlermessage方法,这个方法一个回调方法,我们是必须实现的,否则Handler什么都不会做,为什么呢?还记得刚刚说构造Handler的时候我们记录了一个CallBACk的回掉吗?Handler中的这个handlermessage方法一个方法,如果我们重写了这个方法,在回调的时候就会执行我们先写下的代码,也就是接收到消息之后要做什么。 

public interface CallBACk {
 public Boolean handlemessage(message msg);
}

public void handlemessage(message msg) {
}

这里简单说下整个过程: 
当我们实例化一个Handler的子类并重写handlemessage方法之后,这个时候系统已经帮我们做了几个事情 
1.实例化了一个消息队列messageQueue 
2.实例化了一个关联的Looper对象,并让Looper不断的读取消息队列
3.把我们重写的handlemessage方法记录为我们需要回调的方法 
当我们执行Handler的sendmessage方法的时候,系统会把我们传过去的message对象添加到消息队列,这个时候如果Looper读取到了消息,就会把消息派发出去,然后回调handlemessage方法,执行我们设定的代码

以上就是本文的全部内容,希望对大家的学习有所帮助,也希望大家多多支持编程小技巧。

大佬总结

以上是大佬教程为你收集整理的Android Handler消息派发机制源码分析全部内容,希望文章能够帮你解决Android Handler消息派发机制源码分析所遇到的程序开发问题。

如果觉得大佬教程网站内容还不错,欢迎将大佬教程推荐给程序员好友。

本图文内容来源于网友网络收集整理提供,作为学习参考使用,版权属于原作者。
如您有任何意见或建议可联系处理。小编QQ:384754419,请注明来意。
标签: