public class MessageEvents extends Object
Factory to provide the following to application API:
Typically downstream consumers would not subscribe to these events. However it can be useful for mocking clients and so on. If this is of interest to you please refer to the MultiBit HD code (MIT licence) for extensive examples of this that could save you a lot of time.
Modifier and Type | Method and Description |
---|---|
static void |
fireMessageEvent(MessageEvent event)
Convenience method to fire a message event
|
static void |
fireMessageEvent(MessageEventType messageEventType,
String source)
A message event without a protobuf message is used for communicating system status changes (e.g.
|
static void |
subscribe(Object subscriber)
Subscribe to events.
|
static void |
unsubscribe(Object subscriber)
Unsubscribe a known subscriber from events.
|
static void |
unsubscribeAll()
Unsubscribe all subscribers from events
|
public static void subscribe(Object subscriber)
Subscribe to events. Repeating a subscribe will not affect the event bus.
This approach ensures all subscribers will be correctly removed during a shutdown
subscriber
- The subscriber (use the Guava @Subscribe
annotation to subscribe a method)public static void unsubscribe(Object subscriber)
Unsubscribe a known subscriber from events. Providing an unknown object will not affect the event bus.
This approach ensures all subscribers will be correctly removed during a shutdown
subscriber
- The subscriber (use the Guava @Subscribe
annotation to subscribe a method)public static void unsubscribeAll()
Unsubscribe all subscribers from events
This approach ensures all subscribers will be correctly removed during a shutdown
public static void fireMessageEvent(MessageEvent event)
Convenience method to fire a message event
event
- The event (e.g. DEVICE_CONNECTED)public static void fireMessageEvent(MessageEventType messageEventType, String source)
A message event without a protobuf message is used for communicating system status changes (e.g. DISCONNECT)
messageEventType
- The message type (e.g. DEVICE_CONNECTED)source
- The client name acting as the source (e.g. "TREZOR", "KEEP_KEY" etc)Copyright © 2013–2018 Bitcoin Solutions Ltd. All rights reserved.