Stefano Bagnara schrieb:
Noel J. Bergman wrote:
Imo we should remove this concept of SPOOL from the message repository.
If one will ever want to implement a spool repository based on a
messagereposirory it will have to store the Mail informations in a
messagerepository way (as Flags, or as custom MimeHeaders).
MessageRepository should not have dependencies on the Mail object.
I'll try to catch up on the avalanche of JAMES e-mail later, but with
respect to this, the plan for JAMES is to separate MAIL and MESSAGE.
And we
might even separate SPOOL from MAIL. I'm focusing on the stuff that
Norman
needs now, and will deal with normalized relational schema later.
--- Noel
I think we simply don't need MAIL. We just need SPOOL, and SPOOL make
use of MESSAGE. The envelope informations are needed while we are
spooling it, but not once we have the message in the user inbox
(either POP3 or IMAP).
Imho we can do this simplification safely: the SpoolRepository is an
extension of MailRepository, so if we'll ever need to use a
MailRepository we can simply use a SpoolRepository instead.
Stefano
+1
Norman
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
