Serge, Why does it need a renewable stream? Once it has read the message & put it in the spool, it should not need to use it any more, right? And in the code I don't see it being used more than once, unless I'm overseeing something.
Shilpa -----Original Message----- From: Serge Knystautas [mailto:[EMAIL PROTECTED]] Sent: Friday, May 10, 2002 11:08 AM To: James Developers List Subject: Re: All incoming mails written to temp file before spooling The problem is that MimeMessageSource requires a renewable input stream, so you'll need to have some way to accomplish that. -- Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com/ Shilpa Dalmia wrote: > In the MimeMessageInputStreamSource class (under james/core), instead of > first storing the message from the inputstream (SMTP input stream) to a temp > file & then buffering it out, what if we buffer it out directly from the > input stream? That way we can avoid 1 disk i/o and also not have to store > the data in memory thus avoiding the danger of an errant sender choking > memory. I tried out this approach & seems to work in my test. Does anyone > see any potential risk or danger in doing this? > > Shilpa > > -----Original Message----- > From: Shilpa Dalmia [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 30, 2002 4:09 PM > To: '[EMAIL PROTECTED]' > Subject: All incoming mails written to temp file before spooling > > > Does anyone know why all incoming mails in James are first written to a temp > file before writing to the spool? Why not instead just keep it in memory? > Its a performance bottleneck. Check the constructor for > MimeMessageInputStreamSource. > > Shilpa Dalmia -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
