On Mon, 18 Jun 2001 10:18, Harmeet wrote:
> > I agree with your observation about the extra load from using
> > MimeMessage. But where/how do you want to remove the usage of
> > MimeMessage, and what alternate approach would you use? Maybe add an
> > extra method on MailImpl
>
> to
>
> > retrieve the message header/body data as a stream?
>
> I was thinking of 2 parts
> - MailRepository would store the logical parts of the message separatly
> - Extra method in the MailImpl to retrieve the logical parts, header, body
> attachment etc.
>
> A Mail Repository that stores (a)originnal Mime message, (b)parts of the
> message
> and (c) a descriptor that allows one to lookup parts would fit the bill
> nicely.
> For example if a web application wants 'helloworld.txt' attachment from
> message 'm-1', it would be nice if the code can go to MailImpl, ask for
> attachment 'm-1', read and stream it, without ever parsing the message
> file.
I would also recomend an "envelope" table. Basically the envelope records the
envelope information (ie who it was received from and who it is delivered to
etc). As this may differ from the headers (especially with BCCs) it needs to
be recorded.
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
