The Controller Service

The 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.

Figure: Publisher/Subscriber Architectural diagram

http://www.blisted.org/tr/attachment/wiki/SpamZilla/Services/Controller/PubSub.png?format=raw

This, 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).