Robert Burrell Donkin wrote:
> > > the current table structure [in trunk] is inefficient.
> > > opinions?
As I said, toss and reboot.
We need to change the data storage scheme. As a strawman, we should
separate spool, mailbox and message store.
The message store is simple: the message. Once a message is in here, it
need not be moved, it is just referenced.
The mailbox should serve the needs of both POP3 and IMAP. It contains no
actual message content, delegating to the message store.
Spool contains the spool records. Conceptually, the mail object, which
means SMTP envelope, spool state, message meta-data, etc.
Personally, since I do not really care that much about IMAP (although once
we have it, I would like to see, and possibly contribute to, calendar and
contacts beind added), I am concerned with the message store and spool; a
simple mailbox sufficient for POP3 is fine by me. But you'll want more than
that, and that's fine.
I also want a transactional store, so that we can ensure that once a message
enters a processor, the processor either completes, or any changes are
rolled back. Having all of the stores on top of the same underlying
relational database means not requiring XA.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
