On Fri, 2003-02-21 at 23:06, Mark Crispin wrote: > 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.
But a view is created whenever Pine wants to do sorting. Or some of the filter messages, I think. Doesn't matter what you call it, it's still an array that is frequently done a near-full-scan to find messages. > That is > something that would have also to be done (and be much slower) in a UID > client that had the same functionality. Why slower? I think the code would be very similiar, with the exception that the view_to_uid array would need less updating when handling expunges (one memmove(), vs. memmove() + updating several seq. numbers). > Persistant caching is only good if a user sticks to one or two dedicated > machines. I don't know anyone who accesses their mail from more than a few computers. I use IMAP only at home for accesssing my mails, elsewhere I just ssh into my server and read the mails there. Good and secure ssh clients are easier to find and setup than IMAP clients.
