--On Friday, July 11, 2003 7:05 PM -0700 Mark Crispin <[EMAIL PROTECTED]> wrote:
| I'm sorry to be the bearer of bad news on this. The good news is that if | you implement THREAD=REFERENCES and do so correctly (unlike Courier which | does not), users of clients that use it will bless you since you will | greatly speed up their performance.
Unfortunately I have of late been running more and more into the problem of users wanting to THREAD very large mailboxes and complaining when it takes a long time. They are not keen on restricting the input message set to e.g. just unseen or messages sent within a recent period of time. I would strongly urge server implementers to look beyond merely caching references headers, and to come up with smart caching of the actual thread tree structure itself. Failing that clients will have to drop back to doing client-side caching of all the data in order to make handling large mailboxes an acceptable experience for the user - that kind of defeats the purpose of THREAD in the first place.
-- Cyrus Daboo
