On 10/28/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
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.
Yes, some. And that has always been my goal (as you know).
I agree that we need more experience/input before the API is locked in stone.
What I'm struggling with is this dilemma.. If we move api dev away from server-dev too quickly then the API changes and James-server just carries on with o.a.j.services OTOH if it stays in "server" we aren't strict enough with compliance and/or lifecycle. What to do? well at the moment I think that we evolve it out of server, and *then* give it its own list, but I'm open to suggestion. d.
