james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Serge Knystautas <ser...@lokitech.com>
Subject Re: Missing Mailet APIs related to attributes?
Date Sun, 21 Mar 2004 05:06:05 GMT
Noel J. Bergman wrote:
> Seems to me that we either need to add:
>   sendMail(Sender, Recipients, Message, State, Attributes);
>   sendMail(Sender, Recipients, Message, Attributes);
> or make it easier for developers to create a new Mail instance, which pretty
> much means the same sort of parameters, since Sender and Recipients are
> read-only properties.
> Meanwhile, we can create a MailImpl when we need them.

I don't like the idea of exposing MailImpl, and it seems we're already 
cheating in this regard.  I would prefer deprecating all existing 
sendMail() methods and instead do:

public interface MailetContext {
   Mail newMail();
   void queue(Mail mail);

I'm not wedded to the two names.  I like queue(Mail) over send(Mail) 
because send() implies a) it's going some place else and b) does not 
address how message could be placed in other states (like spam, error, 

Serge Knystautas
Lokitech >> software . strategy . design >> http://www.lokitech.com
p. 301.656.5501
e. sergek@lokitech.com

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message