james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shilpa Dalmia <Shi...@PostX.com>
Subject RE: All incoming mails written to temp file before spooling
Date Fri, 10 May 2002 17:47:47 GMT
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:Shilpa@PostX.com]
Sent: Tuesday, April 30, 2002 4:09 PM
To: 'james-dev@jakarta.apache.org'
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:james-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@jakarta.apache.org>

--
To unsubscribe, e-mail:   <mailto:james-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@jakarta.apache.org>


Mime
View raw message