Some questions and proposals for the MailetAPI and other classes.
1) Can we change MailRepository (and hence the file and db
implementations) to use mailet.Mail not james.core.MailImpl? I can't see
any obvious need to use a specific class rather than a type.
2) Someone (Serge, I think) has noted in mailet.Mail that there are
several methods which don't really belong there: clear(); setSender(),
setRecipients(), setRemoteHost(), setRemoteAddress(). I agree they
shouldn't be here. To these I would add: setName() and setMessage(). I
thought the point of the Mailet API was for mail processing, in which
case users of the Mailet API shouldn't need/ be able to create messages
(they can duplicate them). Creating messages (ie within the mailserver)
is handled by the SMTP server (or an IMAP for drafts). These methods
belong in an implementation specific interface, something like
RecyclableMail. But I don't think we recycle Mail objects, so they are
unnecessary.
Thoughts?
Charles
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
