Noel J. Bergman wrote:
Stefano Bagnara wrote:
I'm refer to any general idea of using JavaMail for local storage.
Shouldn't this discussion be supported by benchmarks?
See the various analysis of JavaMail done by ... IIRC ... Jason Webb from years
ago after I suggested using JavaMail in the first place.
I just searched a lot of old messages but I cannot find the analysis of
JavaMail done by Jason Webb: can you point me to an url with the topic?
I'm interested in reading it because javamail is publishing much more of
its internals nowadays and maybe it is possible to workaround its
limitations: but I need to know what the problem was!
The other important thing is that we stop using JavaMail internally unless we need to
manipulate the contents of the message. MIME4J will be faster, more reliable in the face
of a real-world corpus (doesn't throw exceptions "all the time", unlike
JavaMail), and has a smaller footprint.
--- Noel
Ok, but Mime4J does not provide an API for message persistence, so we
can't use Mime4J to store messages.
And I'm not sure I agree with the "more reliable" statement: mime4j has
not a big userbase like javamail had so I think it's not fair to think
that it is more reliable. I at least found one thing that is not handled
in an rfc compliant way (I don't remember what, now, but I noticed this
while looking the source code to understand how it was parsing headers).
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
