What is the event bus pattern? Let’s quote the documentation of Guava:
publish-subscribe-style communication between components without requiring the components to explicitly register with one another (and thus be aware of each other). It is designed exclusively to replace traditional Java in-process event distribution using explicit registration.
Our team addressed the problem present in other popular Android event bus implementations – the lack of fine-grained delivery thread control. gimBUS allows us to define which thread will be used for the delivery of an event object using the receiver’s method annotation. We are also introducing an experimental feature – sticky events, which – after sending – will be delivered to every new subscriber. Let us know if your usage pattern requires time-limited sticky event implementation. We thought about it but have decided to wait with its implementation until we hear some feedback.
GitHub project: https://github.com/PGSSoft/gimBUS
As gimBUS is an open-source project licensed under the MIT license, everyone is free to fork it and use it. Pull requests are welcome!
Company ad: Are you a fan of open source and free software? PGS Software gives you a chance to contribute your effort to open-source projects. Join today!
Credits: Łukasz Płomiński (architecture and development), Bartosz Stokrocki (maven, travis, repository).
PS: “Gimbus” is a colloquial name for school bus in Poland.