Hello,
(moving this to dbmail-dev)
> My vision here is a "fastheaders" table which has a message number and
> half a dozen columns defined. On some regular basis, or upon message
> insertion, the messageblks table is scanned and the first entry of each
> new message number, which is the header, is parsed for these fast headers
> and they are stored for future searches and quick/short header listings.
An idea we've started (not completed) implimenting in weDBmail
along these lines is dynamically parsing/caching the headers. Any
time the message headers are requested, it'll check the "header cache"
table and use entries if found, but if not, it'll parse the headers
from messageblks and use the results while saving appropriate ones in
the cache. Could make the pop3 and imap servers do that as well.
--
Jesse Norell
jesse (at) kci.net
(moving this to dbmail-dev)
> My vision here is a "fastheaders" table which has a message number and
> half a dozen columns defined. On some regular basis, or upon message
> insertion, the messageblks table is scanned and the first entry of each
> new message number, which is the header, is parsed for these fast headers
> and they are stored for future searches and quick/short header listings.
An idea we've started (not completed) implimenting in weDBmail
along these lines is dynamically parsing/caching the headers. Any
time the message headers are requested, it'll check the "header cache"
table and use entries if found, but if not, it'll parse the headers
from messageblks and use the results while saving appropriate ones in
the cache. Could make the pop3 and imap servers do that as well.
--
Jesse Norell
jesse (at) kci.net