The separated fields are really useful as it means you can show a message listing using a simple join in SQL. Just having the headers flagged or in a separate msgblk means you need to process and interate every visible message, every time you show a mail listing -- very innefficient, unless you use complicated caching schemes/etc.
On the other hand - simply parsing the headers into your native presentation format, means this is only done once and pulling up a mailbox listing takes milliseconds of CPU time rather than ... . I appreciate every doesn't necessarily want this, so maybe having it as compile-time included code would mean that those of us using webmail interfaces can simply turn it on. /Mark > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Ricardo Andere de Mello > Sent: Thursday, 4 December 2003 2:11 p.m. > To: dbmail@dbmail.org > Subject: Re: [Dbmail] 2.0 and header-cache > > Em Quarta 03 Dezembro 2003 20:27, Mark Mackay - Orcon escreveu: > > > Is 2.0 going to have any type of header cache (something > that's suited to > > the native-webmail clients everyone's no-doubt hacking away at? We > > implemented some patches to 1.x and posted them to a list a > while back > > which cached the: > > I would apreciate a kind of mime reference table too (not > necessarily separate > the mimes, just a reference table with mime boundaries and > mime headers). > I don't like to scan all the message to decode the mime, > since it was scanned > to enter at the system at the first place. > > []s, gandhi > > -- > Ricardo Andere de Mello > Quilombo Digital - Presidente > [EMAIL PROTECTED] - 55 11 32717928 > _______________________________________________ > Dbmail mailing list > Dbmail@dbmail.org > https://mailman.fastxs.nl/mailman/listinfo/dbmail >
