On Fri, Jul 28, 2006 at 10:41:19AM +0200, Daniel Eckl wrote: > > > Andrew Findlay schrieb: > >On Fri, Jul 28, 2006 at 12:18:12AM -0700, Nikola Milutinovic wrote: > > > >>So, perhaps we could state that the desired behavior of any IMAP > >>client would be to fetch only those message headers it nedds to and > >>perhaps a bit more. In case of TB, that would transalte to fetching > >>only headers that would be visible to the user and perhaps > >>screenful of header up and down. > > > >It also helps if the clients ask for a limited set of headers from > >each message of interest. > > Yes, I want to second all these statements. That would be my prefered > solution, too. > > By the way: I checked kmails behavior. It fetches the headers of all > mails in a folder, too, but I think it uses just the limited set of > headers and that's why it is so incredible fast compared to thunderbird. Might it not be better to have Cyrus 'learn' what header lines are needed, rather than just bloating the list with more headers. The set of headers would needed to be dynamically changable. The points are: 1) different IMAP clients want different sets of headers. The same IMAP client at different releases might change the set requested. 2) most individual sites run only 2 or 3 different IMAP clients, why get Cyrus to collect the headers that the IMAP clients at that site don't want. 3) most system admins don't have the skills/inclination/... to optimise the set of headers cached. -- Alain Williams Parliament Hill Computers Ltd. Linux Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 http://www.phcomp.co.uk/ #include <std_disclaimer.h> ---- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
