Changes between Version 5 and Version 6 of Document/Development/Design/Framework/EventArchitecture

Timestamp:

07/04/07 23:25:37 (6 years ago)

Author:

ejhernandez@… (IP: 87.217.136.136)

Comment:

Updating current event architecture

Document/Development/Design/Framework/EventArchitecture

@@ -9 +9 @@
 === `Event Watcher` ===
 
-It will be the subject (Observer pattern) which intends to call all the registered watcher to get known if any event has ocurred. An `ebox-watcher` will be installed at '''cron''' that it will check every steptime for executing any script.
+It will be the subject (Observer pattern) which intends to call all the registered watcher to get known if any event has ocurred. An `ebox-watcher` will be executed as a daemon that it will check every steptime for executing any `concrete watcher`. Once an event has been raised, it is sent to the `Event Dispatcher` which dispatches the event to the dispatchers that the event watcher decides. If any dispatcher is not plugged, the event is not sent over this dispatcher. This issue is silently ignored.
 
 === `Concrete Watcher` ===
 
-It will be one the watcher. An example could be a `DiskFullWatcher` which takes care if the disk is full to fill it out more. It will be called by `ebox-watcher` whenever its periodicity says so.
+It will be one the watcher. An example could be a `DiskFullWatcher` which takes care if the disk is full to fill it out more. It will be called by `ebox-watcher` whenever its periodicity says so. Every watcher can decide to where the event will be dispatched, '''any''' is an option to send everywhere possible.
 
 === `Event Dispatcher` ===
 
-Called everytime a new event has been raised, it will dispatch all the new events registered to the registered dispatcher depending on the possibilities.
+It receives events from the `event watcher`. Its burden is sending the event to where the event says so depending on the possibilities.
 
 === `Event Concrete Dispatcher` ===