I remember discussing it, parseing a message into its MIME components is intensive work (I've written a MIME parser) and should be deferred until it is needed, then not repeated.
d. > -----Original Message----- > From: Serge Knystautas [mailto:sergek@;lokitech.com] > Sent: 20 October 2002 00:00 > To: James Developers List > Subject: Re: Latest diffs, source code > > > Yes, you're wrong. The whole point of the class (and related ones) is to > avoid loading and parsing the message into memory. This improved > performance by an order of magnitude back when it was added. > > Serge Knystautas > Loki Technologies > http://www.lokitech.com/ > ----- Original Message ----- > From: "Harmeet Bedi" <[EMAIL PROTECTED]> > To: "James Developers List" <[EMAIL PROTECTED]> > Sent: Saturday, October 19, 2002 9:47 PM > Subject: Re: Latest diffs, source code > > > > I am suggesting that we keep the byte array in memory for the processing > of > > message. > > > > Isn't this already done ? I thought the mailets end up reading > the entire > > mime message, hence loading the data in at least once. Could be > wrong, but > I > > thought there were places that forced entire message load. > > > > Leveraging this info we could remove the temp file. However I admit, it > has > > been a long time since I profiled James. > > > > Harmeet > > > > -- > 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>
