Are you looking at memory that is USED in the heap, or simply the allocation
that the JVM takes from the OS? The former would be something we can fix.
The latter may not, although I know that there is one place in specific
where we can make a fix. When we use
javax.mail.Internet.MimeMessage(MimeMessage) we pay a costly penalty because
that constructor loads the entire message into the heap.
Personally, as someone who used to write real-time, message-passing,
operating systems for a living, JavaMail's implementation offends my sense
of proper coding. But I have some idea as to how to fix the problem
described above, at least within James.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
