Noel J. Bergman wrote: ...
Stephen , all, we have already discussed this at lengths, and the conclusion has been that Mailet API has to be indipendent of Avalon.I don't care which container we're operating in. And people seem fairly firm regarding a Mailet API that works well within an Avalon container, but is not tied to requiring one.
This is their community decision, which I totally respect, and that has evident good points too.
One thing that has polluted in the past this decision, IMHO, is that Avalon can easily be regarded as a whole, and Paul has gone to extents to explain this in (painful? ;-P ) detail.
Mixing my views and the results of the James discussion, I have come to the personal conclusion that it would be cool to have:
- mailet API indipendent on Avalon
* very lightweight, no concerns about config, logging, etc
* it makes possibly unportable mailets
- mailet Avalon profile
* mailets that are also Avalon components, thus gaining
Avalon features
* mailets can be more portable and feature rich
1 cent's worth...
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
