Date: Tue, 22 Jun 2004 10:41:42 +0100 (BST) From: Jan Grant <Jan.Grant@bristol.ac.uk> To: Bill Moran <wmoran@potentialtech.com> Cc: questions@freebsd.org Subject: Re: [OT] Re: What's the best possible email failover solution Message-ID: <Pine.GSO.4.58.0406221039470.8600@mail.ilrt.bris.ac.uk> In-Reply-To: <20040621204111.6e684d45.wmoran@potentialtech.com> References: <20040621132006.2b1a296f.wmoran@potentialtech.com> <20040621172520.3544d6fe.wmoran@potentialtech.com> <20040621214348.GB63857@happy-idiot-talk.infracaninophile.co.uk> <40D76DA3.9090809@mac.com> <20040621204111.6e684d45.wmoran@potentialtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 21 Jun 2004, Bill Moran wrote: > During my research of the IMAP protocol, I determined that _the_best_ > way to store email for high-performance would be to put them in a > database. This is because IMAP doesn't see email as a big blob of > text like POP does. It sees the headers as one thing, and the > different MIME parts of the email each as a seperate thing that can > be fetched independently of the other MIME parts. This is a pretty > good layout for a one -> many relationship in a database. Fact is, > every current IMAP server that I'm aware of has to break emails > apart on the fly in order to server IMAP. Have a closer look at the cyrus layout. Each message is in a single file, true, but they are also preparsed to extract the data required for common IMAP operations. The index files contain things like preformed bodystructure responses and offsets to each mime piece. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/ HP-unix: Open Sauce product, available in 57 distributions.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.58.0406221039470.8600>