Pierre van Rooden wrote: > Michiel Meeuwissen wrote: > >Mailing is something which you may want to do in a lot of > >applications, and the one interface with 2 implementations are hardly > >bloating mmbase.jar itself. > > The point is: is sending email a core functionality of MMBase? > I think it is not, so I don't think it appropriate to have a mail > implementation in the core. I prefer one email application.
My point was that the current email application is not about the sending of email itself. It is about providing an object model to drive it, and is something much more specific then 'sending email'. Since email functionality requires configuration, I think it may be a good idea to centralize that as much as possible, for wich the SendMail Module may be useful. You may doubt if the interface is needed. I'd say that one good implementation should suffice (sending email is sending email...) It would be silly to install the current email package only if you made a module or so which occasionally wants to send a mail, and I foresee that people are not going to do that, but will simply implement their own email configuration then (hey, it can not be more than 10 lines!), making MMBase less maintainable for an administrator. I think it is pragmatic to have the sending email functionality (as one or two class) as a core functionallity, tough perhaps org.mmbase.module. would be a silly location. > If there is to be a core email functionality it should be something that > is simple (just send an email using java mail) and works. Yes, that is also what I mean. A straight and simple sending-mail wrapper for java-mail, only mmbase-ifying / simplifying the configuration of it. Michiel -- Michiel Meeuwissen mihxil' Mediacentrum 140 H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US
