Can someone please explain the context for this discussion? I was not
entirely paying attention, and it seems to have come from elsewhere, but
these items DEFINITELY caught my attention:
> I think I could also offer my +0.5 in terms of contributing MIME
> specific code.
> allow me to suggest MIME related classes be folded into Commons-Codec
> instead of being spawned as a separate project. MIME classes would
> inevitably require several codecs (Base64 and quote-printable encoding
> at the very least) to be of any use in applications targeting
> international audience, primarily due to the fact that per definition
> non-ASCII characters in MIME headers must be escaped.
> I really like the model for handling multipart content currently
> maintained in HttpClients MultipartPost method. For the most part, your
> going to either have content in memory or in a file on the filesystem,
> generically wrapping any "Part" including references to a file in the
> filesystem allows one not to have to put it into memory and still
> process it into the Writer/Stream without the user really needing to
> manage it.
> If there is a consideration to work on the SMTP implementation. This is
> an excellent approach to consider.
One of the issues we have in James is the fact that JavaMail wants to do
everything in memory, so we have limited abilities to parse and manipulate
large messages. I have a project item on my plate to work on addressing
that issue, so any discussion of code for parsing and processing MIME for
SMTP messages has my immediate attention. I had started looking (NIH is a
place in DC, not an attitude for a programmer) elsewhere for code (Java or
C/C++), but had not yet found what I need.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
