Noel J. Bergman wrote:
+1 to the J2EE pattern. I've always thought of mailets as similar to servlets, and I think there is a lot of people who are skilled with this pattern.My proposal is a resource-based model. I will explain this model in J2EE terms, although were there some decision to use Avalon lifecycle methods in the Mailet API, we could invert the pattern. In either case, the same thing happens: the matcher or mailet gets a resource. The key is that we keep this out of the Mailet API, and use standard Java APIs. This is a good thing, in my view.
--
Serge Knystautas
President
Lokitech >> software . strategy . design >> http://www.lokitech.com/
p. 1.301.656.5501
e. [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
