title: Android Event Bus Alternative
body: <p>Context: In a previous Android application I have developed, I used an <strong>event bus</strong> (<strong>otto</strong> by Square) to handle async task results (for example: the result of a server request is posted on the bus and somewhere in the application I intercept that response). Although it did the job, in some article I've read it was mentioned that using such a bus is rather a bad idea as it's considered an <strong>antipattern</strong>. </p>
  
  <p>Why is that so? What are some alternatives to using an event bus when dealing with results of async operations? I know that, most of the time, there is no standard way to handle things, but is there "a more canonical" method?  </p>