Override point dispatch, package protected about otto HOT 7 CLOSED

We probably should hide dispatch better. What's your use case?

from otto.

Please don't. I am extending Bus to dispatch only on the UI thread (if it is going to an activity or a fragment). I was going to make a suggestion for Otto to do this by default, but then I heard a talk on infoq from Eric Burke and he said Square had internally debated that and decided against it, due to some ordering or something..

from otto.

Any reason you aren't moving to the main thread in post(Object)?

from otto.

Because I don't want all events to come off of the event thread only certain ones and probably at certain times. Some would be going to DB, for example getting from the web and then posting to another service to write to the db. Really taking the class doing 1 thing to an irritating level =-).

from otto.

Even better would be if I could have my own EventHandler be used by Otto (via a factory method or the likes) and then in my dispatch I wouldn't have to do any instanceof checking. Custom annotation would specify to be notified on UI thread.

...

Ignore the instanceof comment, just realized that won't work at all.

from otto.

Version 2 adds Handler and Producer interfaces to the public API as a consequence of using code-generation so I suppose there's the possibility of using your own. Will have to think on this a bit.

from otto.

#108 is the solution for this. Guava is looking to implement annotations which map to Executors on which the callbacks get run. A @MainThread annotation could run on one which wraps the main thread Handler. Closing since this issue is now redundant with that one.

from otto.