Danny Angus wrote:
On 11/11/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
That isn't part of the Mailet API at all, and doesn't belong there
IMO. In
JAMES, we have pluggable in-protocol handlers that are connected to such
events. I do not know that anyone wants to standardize on our
in-protocol
plug-in architecture, which we're still evolving, but that seems separate
from Mailets.
I agree that it is separate from mailets, but theres no reason why it
couldn;t be another independant API which others could implement, It
does solve the problem by providing an abstraction and it would be (as
we already know) a different way to invoke some of the same underlying
services, so there are some similarities.
yeah, i agree with Noel that it shouldn't be part of the actual class:
org.apache.mailet.Mailet
But it should be another interface, that sits within the
[org.apache.mailet] package.
Isn't the Mailet API everything under this package?
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?
please forgive me, i have just joined the list, so i am a little unclear
as to the scope of this list and the scope of Mailets.
