Which EventBus is preferable for new Desktop Applications? [closed]
Asked Answered
S

0

9

For several years we use org.bushe.swing.event.EventBus for mainly swing desktop applications. The API is really consistent, and easy to use. But now new requirements have arrised and its desired, that some EventSubscribers should get prefered over others, since they are informed synchronisly. So some kind of priority factor is needed for those subscribers.

Extending EventBus to priorize EventSubscribers shouldnt be that much of a problem, but since org.bushe.swing.event.EventBus has gone stale, I am not sure, if it might be preferable to change the EventBus Implementation.

org.bushe.swing.event.EventBus itself recommends projects like GWT Eventbus for GWT. I'm not sure, if that is also a good approach for swing applications. Which EventBus Implementations do you usually use? Do you may even know a simple Implementations which supports Priorities for Subscribers?

Sextain answered 20/6, 2013 at 8:23 Comment(2)
Maybe this comparison will be useful to you codeblock.engio.net/?p=37.Suppliant
Thats a perfect start for getting an overview over Eventbus Implementations. The document even states, that bushe.EventBus has already the possiblity of priorize handlers, which I didn't know yet. I'll have a closer look. thanks!Sextain

© 2022 - 2024 — McMap. All rights reserved.