Hi, I *know* we've discussed this before, 'till we were almost ready to hit one another ;-) but here goes with a proposal.
PROPOSAL: 1 Repositories. Repositories MUST be available in all implementations of the API. There is no concept of an implementation which only allows for pass-through processing because storage is always required for spooling. There is a concept of processing which has no users registered, however this does not remove the concept of users per-se, a post master is always required. Implementations MAY implement service look up using JNDI however not all implementations would necessarily want the overhead of JNDI. Therfore I propose that accessors are placed in MailetContext to allow mailets to get User and Mail repositories by name. This does not preclude implementations of these methods from using JNDI in the background. 2 optional services A framework for deploying and accessing optional services is required. I propose that these services (eg datasources, spam scanners, dns etc) be looked up in JNDI and that the API include a naming convention for their registration. discuss.. d.
