前面已經(jīng)說了EventBus的基本用法,下面我們一步步的看下Eventbus中到底做了些什么,為什么使用Index就讓性能得到了提升探孝。
注冊
1、獲取EventBus實例
public static EventBus getDefault() {
if (defaultInstance == null) {
synchronized (EventBus.class) {
if (defaultInstance == null) {
defaultInstance = new EventBus();
}
}
}
return defaultInstance;
}
通過這種雙重校驗鎖的方式獲取單例神帅,當(dāng)然獲取實例的方式還有其他方法再姑,但是強烈建議你使用這種方式,否則你會遇到一項不到的事情找御。
2元镀、注冊
public void register(Object subscriber) {
Class<?> subscriberClass = subscriber.getClass();
// 查找注冊類中監(jiān)聽的方法(通過注解或者索引)
List<SubscriberMethod> subscriberMethods = subscriberMethodFinder.findSubscriberMethods(subscriberClass);
synchronized (this) {
for (SubscriberMethod subscriberMethod : subscriberMethods) {
// 注冊方法
subscribe(subscriber, subscriberMethod);
}
}
}
在注冊時,首先會通過SubscriberMethodFiner屬性的findSubscriberMethods方法找到訂閱者所有的訂閱方法霎桅;然后遍歷訂閱方法栖疑,對統(tǒng)一訂閱統(tǒng)一類型消息的方法在一個集合里;訂閱類和訂閱方法放在map中做一個映射滔驶,方便后邊的反注冊遇革。
3、SubscriberMethodFinder查找方法
List<SubscriberMethod> findSubscriberMethods(Class<?> subscriberClass) {
List<SubscriberMethod> subscriberMethods = METHOD_CACHE.get(subscriberClass);
if (subscriberMethods != null) {
return subscriberMethods;
}
// 默認為false,只有指定ignoreGeneratedIndex=true才會為true
if (ignoreGeneratedIndex) {
// 使用反射查找
subscriberMethods = findUsingReflection(subscriberClass);
} else {
// 使用索引
subscriberMethods = findUsingInfo(subscriberClass);
}
if (subscriberMethods.isEmpty()) {
throw new EventBusException("Subscriber " + subscriberClass
+ " and its super classes have no public methods with the @Subscribe annotation");
} else {
METHOD_CACHE.put(subscriberClass, subscriberMethods);
return subscriberMethods;
}
}
SubscriberMethodFinder的findSubscriberMethods首先會通過緩存找到揭糕,找到了就返回萝快,找不到就繼續(xù)找,查找方式有兩種反射和索引著角,主要通過ignoreGeneratedIndex揪漩,這個屬性默認為false,首先進行索引找到吏口,索引未找到時才會啟動反射查找
4奄容、反射查找
private List<SubscriberMethod> findUsingReflection(Class<?> subscriberClass) {
FindState findState = prepareFindState();
findState.initForSubscriber(subscriberClass);
while (findState.clazz != null) {
findUsingReflectionInSingleClass(findState);
findState.moveToSuperclass();
}
return getMethodsAndRelease(findState);
}
private void findUsingReflectionInSingleClass(FindState findState) {
Method[] methods;
try {
// This is faster than getMethods, especially when subscribers are fat classes like Activities
methods = findState.clazz.getDeclaredMethods();
} catch (Throwable th) {
// Workaround for java.lang.NoClassDefFoundError, see https://github.com/greenrobot/EventBus/issues/149
methods = findState.clazz.getMethods();
findState.skipSuperClasses = true;
}
for (Method method : methods) {
int modifiers = method.getModifiers();
if ((modifiers & Modifier.PUBLIC) != 0 && (modifiers & MODIFIERS_IGNORE) == 0) {
Class<?>[] parameterTypes = method.getParameterTypes();
if (parameterTypes.length == 1) {
Subscribe subscribeAnnotation = method.getAnnotation(Subscribe.class);
if (subscribeAnnotation != null) {
Class<?> eventType = parameterTypes[0];
if (findState.checkAdd(method, eventType)) {
ThreadMode threadMode = subscribeAnnotation.threadMode();
findState.subscriberMethods.add(new SubscriberMethod(method, eventType, threadMode,
subscribeAnnotation.priority(), subscribeAnnotation.sticky()));
}
}
} else if (strictMethodVerification && method.isAnnotationPresent(Subscribe.class)) {
String methodName = method.getDeclaringClass().getName() + "." + method.getName();
throw new EventBusException("@Subscribe method " + methodName +
"must have exactly 1 parameter but has " + parameterTypes.length);
}
} else if (strictMethodVerification && method.isAnnotationPresent(Subscribe.class)) {
String methodName = method.getDeclaringClass().getName() + "." + method.getName();
throw new EventBusException(methodName +
" is a illegal @Subscribe method: must be public, non-static, and non-abstract");
}
}
}
反射遍歷每一個方法,然后通過注解和參數(shù)進行校驗产徊,放在FindState的subscriberMethods集合里面
5昂勒、使用索引查找
private List<SubscriberMethod> findUsingInfo(Class<?> subscriberClass) {
FindState findState = prepareFindState();
findState.initForSubscriber(subscriberClass);
while (findState.clazz != null) {
findState.subscriberInfo = getSubscriberInfo(findState);
if (findState.subscriberInfo != null) {
SubscriberMethod[] array = findState.subscriberInfo.getSubscriberMethods();
for (SubscriberMethod subscriberMethod : array) {
if (findState.checkAdd(subscriberMethod.method, subscriberMethod.eventType)) {
findState.subscriberMethods.add(subscriberMethod);
}
}
} else {
findUsingReflectionInSingleClass(findState);
}
findState.moveToSuperclass();
}
return getMethodsAndRelease(findState);
}
重點是在findUsingInfo里面調(diào)用了getSubscriberInfo方法,這個方法遍歷調(diào)用索引的getSubscriberInfo方法舟铜,返回空則進行下一個戈盈,不為空直接返回結(jié)果。如果查找了所有的索引都沒有那么會使用findUsingReflectionInSingleClass使用反射查找谆刨,那遍歷的索引是在EventBusBuilder
的addIndex方法中加入的奕谭。
6、找到方法之后痴荐,還要進行注冊血柳,這里一步是方便后面的發(fā)布消息以及取消注冊的操作
private void subscribe(Object subscriber, SubscriberMethod subscriberMethod) {
Class<?> eventType = subscriberMethod.eventType;
Subscription newSubscription = new Subscription(subscriber, subscriberMethod);
CopyOnWriteArrayList<Subscription> subscriptions = subscriptionsByEventType.get(eventType);
if (subscriptions == null) {
subscriptions = new CopyOnWriteArrayList<>();
// 方便發(fā)送消息的操作
subscriptionsByEventType.put(eventType, subscriptions);
}
// 省略部分代碼
// 優(yōu)先級
int size = subscriptions.size();
for (int i = 0; i <= size; i++) {
if (i == size || subscriberMethod.priority > subscriptions.get(i).subscriberMethod.priority) {
subscriptions.add(i, newSubscription);
break;
}
}
// 方便后面的反注冊操作
List<Class<?>> subscribedEvents = typesBySubscriber.get(subscriber);
if (subscribedEvents == null) {
subscribedEvents = new ArrayList<>();
typesBySubscriber.put(subscriber, subscribedEvents);
}
subscribedEvents.add(eventType);
}
這里主要有兩個Map:subscriptionsByEventType和typesBySubscriber,消息函數(shù)參數(shù)->所有的訂閱方法生兆,訂閱類->訂閱方法难捌。到此EventBus的注冊功能結(jié)結(jié)束了,我們來看下他的時序圖
消息發(fā)送
1鸦难、通過調(diào)用EventBus的post方法即可完成消息的發(fā)送根吁,在post方法中調(diào)用了postSingleEvent方法,postSingleEvent方法會繼續(xù)調(diào)用postSingleEventForEventType方法
private boolean postSingleEventForEventType(Object event, PostingThreadState postingState, Class<?> eventClass) {
CopyOnWriteArrayList<Subscription> subscriptions;
synchronized (this) {
subscriptions = subscriptionsByEventType.get(eventClass);
}
if (subscriptions != null && !subscriptions.isEmpty()) {
for (Subscription subscription : subscriptions) {
postingState.event = event;
postingState.subscription = subscription;
boolean aborted = false;
try {
postToSubscription(subscription, event, postingState.isMainThread);
aborted = postingState.canceled;
} finally {
postingState.event = null;
postingState.subscription = null;
postingState.canceled = false;
}
if (aborted) {
break;
}
}
return true;
}
return false;
}
postSingleEventForEventType方法通過subscriptionsByEventType獲取消息類型對應(yīng)的Subscription集合,Subscription封裝了實例和訂閱方法名合蔽,這樣我們就可以進行調(diào)用了击敌。
2、執(zhí)行訂閱方法拴事,找到Subscription之后沃斤,就會遍歷執(zhí)行postToSubscription方法
private void postToSubscription(Subscription subscription, Object event, boolean isMainThread) {
switch (subscription.subscriberMethod.threadMode) {
case POSTING:
invokeSubscriber(subscription, event);
break;
case MAIN:
if (isMainThread) {
invokeSubscriber(subscription, event);
} else {
mainThreadPoster.enqueue(subscription, event);
}
break;
case BACKGROUND:
if (isMainThread) {
backgroundPoster.enqueue(subscription, event);
} else {
invokeSubscriber(subscription, event);
}
break;
case ASYNC:
asyncPoster.enqueue(subscription, event);
break;
default:
throw new IllegalStateException("Unknown thread mode: " + subscription.subscriberMethod.threadMode);
}
}
在此方法中會根據(jù)Subscription的threadMode來執(zhí)行圣蝎,我們最常用的就Main,我們看到如果當(dāng)前是主線程會直接執(zhí)行衡瓶,如果不是主線程會使用mainThreadPoster徘公,其實這是一個主進程的Handler,這也是為什么我們可以在threadMode=main的訂閱方法中操作UI的原因
3、HandlerPoster的enqueue方法哮针,發(fā)送消息
void enqueue(Subscription subscription, Object event) {
PendingPost pendingPost = PendingPost.obtainPendingPost(subscription, event);
synchronized (this) {
queue.enqueue(pendingPost);
if (!handlerActive) {
handlerActive = true;
if (!sendMessage(obtainMessage())) {
throw new EventBusException("Could not send handler message");
}
}
}
}
首先這里先封裝成PendingPost关面,然后加入隊列,發(fā)送一個空的消息十厢,為啥要這樣搞呢等太?可能是因為直接發(fā)送一個消息過去,不方便傳遞Subscription和Event吧蛮放。
4缩抡、handleMessage
public void handleMessage(Message msg) {
boolean rescheduled = false;
try {
long started = SystemClock.uptimeMillis();
while (true) {
PendingPost pendingPost = queue.poll();
if (pendingPost == null) {
synchronized (this) {
// Check again, this time in synchronized
pendingPost = queue.poll();
if (pendingPost == null) {
handlerActive = false;
return;
}
}
}
eventBus.invokeSubscriber(pendingPost);
long timeInMethod = SystemClock.uptimeMillis() - started;
if (timeInMethod >= maxMillisInsideHandleMessage) {
if (!sendMessage(obtainMessage())) {
throw new EventBusException("Could not send handler message");
}
rescheduled = true;
return;
}
}
} finally {
handlerActive = rescheduled;
}
}
這里回去取出消息,然后再調(diào)用EvenBus的invokeSubscriber方法筛武。這里應(yīng)該是真正執(zhí)行訂閱方法的地方
void invokeSubscriber(Subscription subscription, Object event) {
try {
subscription.subscriberMethod.method.invoke(subscription.subscriber, event);
} catch (InvocationTargetException e) {
handleSubscriberException(subscription, event, e.getCause());
} catch (IllegalAccessException e) {
throw new IllegalStateException("Unexpected exception", e);
}
}
OK缝其,在這里執(zhí)行了invoke方法,訂閱方法被調(diào)用了徘六。
EventBus反注冊
public synchronized void unregister(Object subscriber) {
List<Class<?>> subscribedTypes = typesBySubscriber.get(subscriber);
if (subscribedTypes != null) {
for (Class<?> eventType : subscribedTypes) {
unsubscribeByEventType(subscriber, eventType);
}
typesBySubscriber.remove(subscriber);
} else {
Log.w(TAG, "Subscriber to unregister was not registered before: " + subscriber.getClass());
}
}
包括一下幾個步驟:
1内边、找到訂閱類訂閱的消息類型
2、遍歷消息類型待锈,找到消息類型對應(yīng)的所有的訂閱方法
3漠其、遍歷所有訂閱方法,如果實例等于這個反注冊的訂閱類的進行去除操作(unsubscribeByEventType方法)
4竿音、去除訂閱類到訂閱消息類型的映射
在使用EventBus過程中和屎,一定要取消訂閱,否則會導(dǎo)致內(nèi)存泄漏春瞬。