EventBus源码阅读（1）-ThreadMode

ThreadMode枚举类

这个类最简单了，所以先拿它祭刀。

柿子拣软的捏。

源码如下：

/*
 * Copyright (C) 2012-2016 Markus Junginger, greenrobot (http://greenrobot.org)
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package org.greenrobot.eventbus;

/**
 * Each event handler method has a thread mode, which determines in which thread the method is to be called by EventBus.
 * EventBus takes care of threading independently from the posting thread.
 * 
 * @see EventBus#register(Object)
 * @author Markus
 */
public enum ThreadMode {
    /**
     * Subscriber will be called in the same thread, which is posting the event. This is the default. Event delivery
     * implies the least overhead because it avoids thread switching completely. Thus this is the recommended mode for
     * simple tasks that are known to complete is a very short time without requiring the main thread. Event handlers
     * using this mode must return quickly to avoid blocking the posting thread, which may be the main thread.
     */
    POSTING,

    /**
     * Subscriber will be called in Android's main thread (sometimes referred to as UI thread). If the posting thread is
     * the main thread, event handler methods will be called directly. Event handlers using this mode must return
     * quickly to avoid blocking the main thread.
     */
    MAIN,

    /**
     * Subscriber will be called in a background thread. If posting thread is not the main thread, event handler methods
     * will be called directly in the posting thread. If the posting thread is the main thread, EventBus uses a single
     * background thread, that will deliver all its events sequentially. Event handlers using this mode should try to
     * return quickly to avoid blocking the background thread.
     */
    BACKGROUND,

    /**
     * Event handler methods are called in a separate thread. This is always independent from the posting thread and the
     * main thread. Posting events never wait for event handler methods using this mode. Event handler methods should
     * use this mode if their execution might take some time, e.g. for network access. Avoid triggering a large number
     * of long running asynchronous handler methods at the same time to limit the number of concurrent threads. EventBus
     * uses a thread pool to efficiently reuse threads from completed asynchronous event handler notifications.
     */
    ASYNC
}

这个类很简单，我们自己看注释就能明白。

1、POSTING

默认模式

那个线程提交了发送消息的任务，就在哪个线程中具体处理发送请求，即发送该消息。

我们一般情况下都是用该模式。

2、MAIN

在主线程中具体处理发送请求。即发送该消息。

如果提交消息的线程是(UI)主线程，则直接发送该消息；若提交消息的线程非（UI）主线程，则提交给主线程发送该消息。

3、BACKGROUND

在后台线程中处理发送请求。

如果提交消息的线程为主线程（UI），则启动后台线程处理；如果提交消息的线程为非主线程，则直接在该线程中处理。

4、ASYNC

在一个独立的线程中单独处理。该线程不是提交消息的线程。

同时提醒我们要主要在主线程中处理的时间问题，不要造成NDR错误。

至于他的使用我们先不管，主要目的理解这段代码，读清楚了，看明白了。那好，我们接下来继续往下看。