Brian Blood wrote:
Perhaps if we started with a few really basic headers to base the
implementation on, then peope could extend it on their own past there.
Like From: and Subject:
Actually, now that I think about this, shouldn't these headers just be added
into the messages table?
How about...
Date: (I'm assuming internal_date is something else)
From:
Subject:
Message-ID:
That should cover 98% of what people are looking to accomplish, yes?
I beleive in automatic addition to the header cache,
1 Start with an empty table of headers_to_cache.
2 Client asks for "From:" and "Subject:" headers
Then add these to the headers_to_cache
Add the headers "From:" and "Subject:" to the header
cache
3 Answer the client with the expected answer.
4 The next client asking for "From:" and "Subject:" headers will
get a very fast answer.
This will take a performance hit on the database when new mail
clients are used. But the database should adapt quite fast.
Remember, one mail client should ask for the same headers each in
its limited sets of queries.
We will this way get an almost optimized database for each site.
With a predetermined set of (static) headers to cache, will we
get a (severe?) performance hit with just one header outside the
header cache on every query.
With the system I have suggested will we probably cache a few
headers to much, but I have no idea of how much this would impair
performance.
/Magnus
