Martin Cooper wrote:
> This started from a thread on commons-user entitled:
> [net] Why use Net for SMTP?
> where the question was asked: Given that JavaMail is standard and does the
> job, why would one choose to use the SMTP facilities in Commons Net?
JavaMail is largely oriented for clients, and has a design goal of being
easy to use for programmers, rather than being comprehensive. There are
major problems when we need to deal with large messages. JavaMail expects
JAF to know how to handle each Part, so when trying to process a message, if
there is a MIME type for which JAF doesn't have a mapping, it can throw an
exception simply by loading the message. The officially recommended
solution is to get the raw content stream, but then we're back to needing
our own code to process the contents if we want to do anything more than
transport the blob.
> If we're going to put this MIME thingy together, it would seem that the
> issues being faced by James would provide a nice set of design criteria to
> add to the puzzle. A robust MIME library that would satisfy the needs of
> James, HttpClient, FileUpload, and possibly others, would be awesome.
One capability, which I've mentioned before, that I would like to see
available is stream-oriented regex support. If we could process a set of
regular expressions during stream processing, it would be really helpful for
some applications.
--- Noel
We need this for James. It is pretty close to the top of the list in terms
of addressing issues related to user requests. Let's go for it.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
