From 584a22238d380600c3f7a4c781fb6db0a15ed9a5 Mon Sep 17 00:00:00 2001 From: Ilkka Seppala Date: Sat, 3 Oct 2015 21:06:52 +0300 Subject: [PATCH] Improve Event Aggregator Javadoc --- .../src/main/java/com/iluwatar/event/aggregator/App.java | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/event-aggregator/src/main/java/com/iluwatar/event/aggregator/App.java b/event-aggregator/src/main/java/com/iluwatar/event/aggregator/App.java index 029489077..b69d8ceaa 100644 --- a/event-aggregator/src/main/java/com/iluwatar/event/aggregator/App.java +++ b/event-aggregator/src/main/java/com/iluwatar/event/aggregator/App.java @@ -5,8 +5,12 @@ import java.util.List; /** * - * The Event Aggregator pattern channels events from multiple objects - * into a single object to simplify registration for clients. + * A system with lots of objects can lead to complexities when a client wants to subscribe + * to events. The client has to find and register for each object individually, if each + * object has multiple events then each event requires a separate subscription. + *

+ * An Event Aggregator acts as a single source of events for many objects. It registers + * for all the events of the many objects allowing clients to register with just the aggregator. *

* In the example {@link LordBaelish}, {@link LordVarys} and {@link Scout} deliver events to * {@link KingsHand}. {@link KingsHand}, the event aggregator, then delivers the events