EventBus
is the (virtual) machine wide manager for event
handling.See: Description
Interface | Description |
---|---|
EventBus<E extends org.refcodes.observer.Event<?>,O extends org.refcodes.observer.Observer<E>,EM extends org.refcodes.observer.EventMatcher<E>,H> |
The
EventBus is the (virtual) machine wide manager for
ActionEvent handling. |
EventBusMatcher |
A convenience definition of an
EventMatcher for the ready to use out
of the box EventBusImpl implementation of the generic
EventBus definition. |
EventBusObservable<E extends org.refcodes.observer.Event<?>,O extends org.refcodes.observer.Observer<E>,EM extends org.refcodes.observer.EventMatcher<E>,H> | |
EventBusObserver |
A convenience definition of an
Observer for the ready to use out of
the box EventBusImpl implementation of the generic EventBus
definition. |
EventBusPublisher<E extends org.refcodes.observer.Event<?>> |
The Interface EventBusPublisher.
|
Class | Description |
---|---|
AbstractEventBus<E extends org.refcodes.observer.Event<?>,O extends org.refcodes.observer.Observer<E>,EM extends org.refcodes.observer.EventMatcher<E>,H> |
The Class AbstractEventBus.
|
EventBusImpl | |
EventBusMatcherSugar |
Declarative syntactic sugar which may be statically imported in order to
allow declarative definitions for the
EventBusMatcher elements. |
EventBusObservableImpl<E extends org.refcodes.observer.Event<?>,O extends org.refcodes.observer.Observer<E>,EM extends org.refcodes.observer.EventMatcher<E>,H> |
This delegate hides any additional functionality away from a caller
concerning the the provides implementation.
|
EventBusPublisherImpl<E extends org.refcodes.observer.Event<?>> |
This delegate hides any additional functionality away from a caller
concerning the the provides implementation.
|
EventBus
is the (virtual) machine wide manager for event
handling. It implements a publish/subscribe mechanism.
"... lately some colleagues and me were reasoning on how to do client-side (Browser, JavaScript) communication between web-page components ... decoupled ... in general I recommend taking a look at an event-bus (aka page-bus), with Java why not take a look at the refcodes-eventbus? ... the following “equation” came to mind … simply speaking, the equation Observer pattern + Publish–subscribe pattern = Message broker solves to refcodes-eventbus ..."
Signaling events to some event-listener … Subscribing your event-listener for some specific events … Publishing events merely to interested event-listeners … Strongly decoupling the publisher and the subscriber … Considering privacy issues (no simple broadcast) …
In the article refcodes-eventbus: Observer + Publish–subscribe = Message broker I describe the refcodes-eventbus accompanied with a plain simple example on how to use it.
The refcodes-eventbus artifact makes use of the refcodes-matcher framework for defining the criteria on when to deliver an event to an event-listener. It also sets on top of the refcodes-observer framework regarding issues around the Observer pattern ... See also "http://www.refcodes.org/blog/publish_subscribe_observe_event-bus"
Copyright © 2017. All rights reserved.