Serge Knystautas wrote:
On 11/11/06, Alan Williamson <[EMAIL PROTECTED]> wrote:
I think originally it was just addressing mail processing in general,
which some people liked because it opened the door for mailets with
other protocols (NNTP, jabber, etc...). I came around to wanting it
exclusively for SMTP. I think that while mime and some other notions
are shared between SMTP, NNTP, and others, the differences are too
wide to have one API effectively solve all those problems.
I'm +1 to adding the handler API stuff into the mailet API.
I don't feel exceptionally strongly about it because we're architected
roughly the same way if I understand
"the handler stuff" correctly (each command is separate with a
reflectional lookup that finds that command)
minus that last step of configuration. However, this design decision is
probably not a great thing to force
with the mailet API for implementors. Assuming other mailservers (say a
postfix) overcame the cumbersome
requirement of Java to plug this in, somehow I doubt they'll be willing
to rearchitect in this manner. Though
the system of queues, message "objects" and listeners is fairly universal.
-Andy
