> > adding processor to the API would allow different implementations to
> > behave differently, so I can live with this the way it is.
> What value do you see to adding Processor to the Mailet API? Forget the
> question of whether Processor extends Mailet or not. What additional
> interface(s) are you trying to provide to matchers and mailets?
Leaving aside the thought of using Mailet interface for Processors for a
moment I think a Processor interface would have a richer configuration and
expose more container lifecycle, see my observation on your point about
listeners for example.
I we already have two different opinions on the behaviour of our linear
processor, this could be easily settled if we had two implementations of
Processor. Plus.. theres the notion of allowing sieve processors and other
processors as API compliant wrappers for other API's and systems, such as
perl anti-spam scripts or whatever, and ... we might arrive at a use for
some less simplistic processor architecture, say a boolean processor
(having two paths), or a "switch/case" processor. I'm just speculating so
don't ask me for use-cases, but I'm keen not to prohibit such flexibility
arbitrarily if allowing it doesn't overly complicate the "contract" which,
in this case I don't believe it does (if that be gramatical;).
> Note that I wouldn't want this (existing) behaviour to be part of the
> contract of Processor, just the implemented behaviour of LinearProcessor.
> Please define what you feel is missing.
RE. v hosting.. Not sure at the moment, all I know is that we didn't have a
fully integrated and comprehensive answer to this last time I paid it any
close attention.
d.
***************************************************************************
The information in this e-mail is confidential and for use by the addressee(s) only.
If you are not the intended recipient (or responsible for delivery of the message to
the intended recipient) please notify us immediately on 0141 306 2050 and delete the
message from your computer. You may not copy or forward it or use or disclose its
contents to any other person. As Internet communications are capable of data
corruption Student Loans Company Limited does not accept any responsibility for
changes made to this message after it was sent. For this reason it may be
inappropriate to rely on advice or opinions contained in an e-mail without obtaining
written confirmation of it. Neither Student Loans Company Limited or the sender
accepts any liability or responsibility for viruses as it is your responsibility to
scan attachments (if any). Opinions and views expressed in this e-mail are those of
the sender and may not reflect the opinions and views of The Student Loans Company
Limited.
This footnote also confirms that this email message has been swept for the presence of
computer viruses.
**************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
