On Tue, Jun 15, 1999 at 02:20:12PM -0500, Brian Zimbelman wrote:
> What are the advantages that make so many of you say the JavaMail api is the
> way to go? I guess if I didn't have the wrapper already written, then I
> would consider JavaMail again, but if it is still as convoluted as it was in
> the past, I would probably just write the wrapper again!
I dug into JavaMail because I was/am working on a Java
email conduit for Palms. I could send email through an SMTP channel,
but that wouldn't let me read email from a mailbox into the Palm.
The JavaMail API uses the concept of "providers" to hide the details
of whether you're talking to an IMAP server, an mbox file, or a
Notes server. SMTP's just another provider, one that can only
send.
JavaMail is, I think, intended to be a client package as
well as a sender. Adding the client package makes things a bit ugly --
it _is_ easy to write a send-only API -- but I don't think I'd
describe it as "convulted".
I used it in a servlet that's supposed to be deployed in
a Notes environment. It's currently using SMTP to send the email,
but if there's a Notes provider package, and the client would prefer
the email go directly to Notes, we could use that without making
more than a single-line code change and updating a properties
file.
--
Robert Crawford [EMAIL PROTECTED]
http://www.iac.net/~crawford
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
