On Fri, 21 Feb 2003, Timo Sirainen wrote: > But whenever sorting is done, there is the sort array that has to be > updated and accessed slowly whenever you get fetch envelope reply > (pine_imap_envelope -> mn_raw2m() -> msgno_in_sort()).
Wrong. What you are seeing in Pine is a mapping from a view. That is something that would have also to be done (and be much slower) in a UID client that had the same functionality. > Also if it's sorted in any way. I guess sequences work well enough for > unsorted mailboxes. They work better than UIDs for sorted or unsorted. > > Since we never fetch everything, we never need to resync everything. Just > > toss out the local cache and do demand-fetching. > Meaning that you toss out a completely usable cache just because you > don't want to use UIDs? Since we never fetch all that much into the cache, there isn't that much cost. Note too that on shared machines a cache that persists beyond sessions is a security bug. Finally, if the user uses multiple machines, then that's a lot of duplication of mail (including sensitive information). Persistant caching is only good if a user sticks to one or two dedicated machines. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate.
