Changes between Version 1 and Version 2 of SpamZilla/Services/Controller

Show
Ignore:
Timestamp:
02/17/06 08:10:10 (5 years ago)
Author:
scottmc
Comment:

Added more details and cross references for controller documentation.

Legend:

Unmodified
Added
Removed
Modified
  • SpamZilla/Services/Controller

    v1 v2  
    33The SpamZilla controller service manages the publication/subscriber framework that SpamZilla is designed around.  The concept is quite simple, a node, during its initialization or startup, will contact a service on another node informing it it wants to listen for one or more possible actions.  The node that was contacted (the publisher) keeps track of these requests (subscriptions), and when actions are made public by being ''published'', each subscriber to that action is contacted, and the call that was published is relayed on to those subscribers. 
    44 
    5 See the diagram attached. 
     5''Figure: Publisher/Subscriber Architectural diagram'' 
     6 
     7http://www.blisted.org/tr/attachment/wiki/SpamZilla/Services/Controller/PubSub.png?format=raw 
     8 
     9This, although the most simple, is the most important function of the SpamZilla application.  As all of the mailer nodes have now been replaced with JavaMail, the controller does little other than relay commands to JavaMail in terms of actually sending e-mail.  All other functioins of SpamZilla revolve around list management, campaign management, and some of the the tracking components still live here (however that will be short lived, certainly).