Serge Knystautas wrote:
Aaron Knauf wrote:I have no opinion on whether or not it is a good idea to treat the Mailet API as a distinct entity. If that is what others want (and I think it has already been decided that they do), I'll get on board. However, Mailet portability is a *must* if we are to do this.
Aaron,
You'll see in the Top-Level-Project proposal, one of the motivators to do this is to create subprojects, namely a project to house the separate mailet API/specification, and also a project to house mailet implementations.
So yes, a big reason why we're james.apache.org is because we've decided we want the Mailet API as a distinct entity.
Yeah, I know this, Serge. The point that I am making (in the statement that you are replying to,) is that I am truly ambivalent about this decision, but quite happy to support it. The point the I was making in that post, was that (IMHO) there is no point in going down that road without achieving the degree of portability in Mailets as has been achieved in servlets.
Cheers
ADK
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
