Danny Angus wrote:
> We either separate [the Mailet API] from James server or we don't.
> I don't think we should yet, because it isn't complete enough in
> itself to allow anyone to really use Mailets in another context.
> Therfore I'm in favour of leaving it for users, and working on
> server-dev@ until we have got the API complete enough to move into
> its own sub-project.
Haven't we heard that others are interested in the Mailet API? Plus, there
are some related messaging use-cases, and we have a fine
messaging/routing/mediation engine.
I agree that we need more experience/input before the API is locked in
stone.
--- Noel
