Danny Angus ha scritto:
I'd be in favour of this, in fact I'd be happy to do all the work on
"std mailets", based on the sandbox work it would only take a couple
of days.
Are you referring to the repositories api and the mailet v3 sandbox?
I'm not sure Robert proposal is related to it.... Robert?
And I would prefer to see a release of the "old stuff" (with minor
changes) using the new reorganized layout before we start to make big
changes to mailet api.
Stefano
On Feb 3, 2008 7:41 PM, Robert Burrell Donkin
<[EMAIL PROTECTED]> wrote:
i think that we should separate the mailet code from the server
codebase in trunk. i can see two easy initial products:
i'm tempted to move quickly to a VOTE since there seems to be a rough
consensus but i'll post this first just in case anyone wants to jump
in with objections, ask for clarifications or come up with improved
names. so now's your chance ;-)
- robert
name: standard-mailets
contents: mailets and mailet utilities decoupled from JAMES server
(see stefano's analysis)
rationale: mailets should be reusable outside JAMES. separating them
from JAMES server is an architectural improvement and means users can
take mailets without having to take the rest of JAMES
name: security-mailets
contents: SMIME, PGP/MIME, security utilities
rationale: security is a specialist area with specific dependencies.
easier to version and release independently.
