Interface MailerIntf

All Superinterfaces:
Serializable

public interface MailerIntf extends Serializable
From within the calendar system we have the following mailing needs:
  • When an event is added/changed/deleted mail the chnage to all subscribers to that events calendar.
  • When an email alarm fires, mail something, including the event, to the alarm receiver

Over time other needs may present themselves.

The subscribed case can be thought of as a mailing list. For each calendar, we have a list of subscribers who want events emailed. When a change occurs to the calendar we send the message out on the list. This interface allows implementors to use a list server to handle the, possibly large amount of, mail generated by this system.

The second case is less easily optimized. Each email is unique in content and usually has only one recipient.

In both cases it is useful to have some sort of mechanism for determining bad addresses. List servers often have their own mechanisms which usually result in a recipient being eventually deleted from the list. Thsi interface allows the calendar system to query the state of a given recipient on the list.

Because we are probably interfacing to a system which identifies users solely by their email-address, we have to give that system the chance to update itself correctly when the users email is changed. We present the new address to the system as well as the old one.

Author:
Mike Douglass douglm@bedework.edu