Matthew T. O'Connor wrote:
I don't think this will work well. I think you will wind up with alot
of headers that you don't want, which translates to a lot of unnecesary
work for the mail injectors. 95% of the time you just need the basic
headers, every once in a while you want to search based on non-standard
headers.
Maybe, but I beleive that the mail clients are quite
simpleminded. Please broaden my view and give me more examples of
when the client requests unusual headers.
I beleive it requests the headers when it displays the content of
the mailbox. When else does it request the headers?
Mail filtering?
Anybody that knows what have any header query request statistics?
<semi-relevant brain storming> I do like the idea of auto selecting the
cached headers, but it needs to be configurable. Perhaps a way to
exclude certain headers from ever being cached, and forcing others to
always be cached. Perhas some type of heuristic, that keeps track of
how often certain headers are being requested, and auto-adding a new
header if requested more than 10% of the time... </semi-relevant brain
storming>
Yes you are right, it should be configurable which headers to
always cache, which to never cache and a threshold level.
The sweet spot in this question, at what level do we create the
lowest database load?
We could create something like a moving average on header requests.
<semi-relevant comment>Try to predict user patterns! You will
almost always be wrong. Instead try to create a system that
adapts to the user pattern, and you would get snappier response.
Compare to the linux interactivity scheduler
</semi-relevant comment>
Magnus
