> I was thinking of 2 parts > - MailRepository would store the logical parts of the message separatly Why? isn't this unneccessarily adding potentially redundant processes to an area which is already identified as a possible bottleneck? And... that means that to store and retrieve an rfc822 message using mime encoding you would parse and split the message, store the parts seperately, retrieve all the seperate parts, then re-construct the original message. I'm sorry but I firmly believe the appropriate place for parseing Mime messages into their component parts is the end user application, which in this case could also be a mailet (just to confuse). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
- [VOTE] Remove model attribute from MailRepositories Charles Benett
- Re: [VOTE] Remove model attribute from MailRepositor... Serge Knystautas
- Re: [VOTE] Remove model attribute from MailRepositor... Harmeet
- RE: [VOTE] Remove model attribute from MailRepositor... Danny Angus
- Re: [VOTE] Remove model attribute from MailRepositor... Serge Knystautas
- Re: [VOTE] Remove model attribute from MailRepositor... Harmeet
- Re: [VOTE] Remove model attribute from MailRepositor... Peter Donald
- RE: [VOTE] Remove model attribute from MailRepositor... Danny Angus
- RE: [VOTE] Remove model attribute from MailRepositor... Danny Angus
- Re: [VOTE] Remove model attribute from MailRepositor... Serge Knystautas
- RE: [VOTE] Remove model attribute from MailRepositor... Danny Angus
- Re: [VOTE] Remove model attribute from MailRepositor... Serge Knystautas
- Re: [VOTE] Remove model attribute from MailRepositor... Harmeet
- Re: [VOTE] Remove model attribute from MailRepositor... Charles Benett
