Danny Angus wrote:
On 11/11/06, Alan Williamson <[EMAIL PROTECTED]> wrote:
I am a little confused as to why Danny/Noel believe it isn't part of the
Mailet API? What is the remit of the Mailet API? What is its purpose
in life if not a hook for developers to process mails?
Yeah, but the API doesn't assume that the system doing the processing
is also implementing any of the mail protocols. It could be that the
mail is all sitting in an archive and needs to be mined for some
reason.
The current API does, we never agreed that this is the final Mailet API
goal.
Imho it is a big limit of the current mailet apis and we should fix it.
Therefore protocol related API's are out of scope, but that doesn't
make it a bad idea.
I don't care if we are in protocol or outside it. I think we only need
to add a finer api that let us to write "portable plugins" (implementing
interfaces defined by our api) that are able to handle a wide range of
usages:
- partial matching (only parts of the current Mail object)
- change tracking api: maybe it could be useful to add listeners/event
to track changes to a Mail, so to know if it is ghosted, duplicated,
rerouted or anything similar.
Imho there are a lot of ways to improve the current mailet apis without
the need to tie to SMTP or other transfer protocols.
Stefano
