Re: Avalon dependance in mailets

[Nicola Ken Barozzi]

Serge Knystautas wrote:

----- Original Message -----
From: "Serge Sozonoff" <[EMAIL PROTECTED]>

From a mailet developers point of view,  I would much rather have the DB
stuff exposed through the Mailet API.
If you really want to go your own way or need something not provided by

the

API you still have the freedom to do so.

For the same reason I don't think mailet API needs to specify logging, I
don't think we need to expose DB stuff through it.  There are other standard
approaches to doing this (that while certainly would get used by mailets,
don't need an API).

I think it would be good to flesh out the mailet specification (instead of
relying on an API to do everything), that describes how mailets might log,
get db connections, etc... (and explain the mailet lifecycle, whatever
else...)

This makes me think...

Essentially the Mailet API won't thus provide portability of mailets between servers, just a common API, right?

Meaning that I cannot simply get a mailet written from James and simply pop it into XMailServer and hope it to run, right?

This could be a strength and a weekness.
Strength because it's easier to learn, implement and to keep focused in development .
Weekness because it's not made to make completely portable mailets.

So what about doing a Mailet spec as defined above and define an additional Avalon Mailet profile, that James could use, to define other aspects like logging, get db connections, etc?

--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>