On 11/12/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
- Mailet API - Handler API - Common Services
I believe that there is a place for all three of these things, and that the first two both depend upon the third one, but that neither of the first two need to be a mandatory requirement of an API which specifies the other one. Lets consider the J2ME jsr standards, there is a core and extensions. Or Portals and CMS, there are a number of standards which can be combined or used in isolation. I think we're really close to agreeing that the scope of an API project can and possibly should include all three (I think we're just getting hung up on names), so that implementors can optionally implement any sensible combination to build any sensible container, but I do still maintain that there are use-cases which do not include a requirement for implementing protocols. One of these is a mail processor which has access to a spool which is filled by something else. This may or may not be a thing which implements the handler api. Another is a piece of client software which uses JavaMail and POP3 or IMAP to aggregate mail from a number of internet accounts. I would be 100% in favour of developing the three API's under the mailet api banner, as long as it was done in a manner which clearly signposted the options which implementors have, and to my mind that has to include seperate names and distinct packages. org.apache.mail.mailet org.apache.mail.handlers org.apache.mail.services d.
