The IMAP code could generally use some work, the current codebase is a little difficult to work with though, so dont expect changes for a while yet.
I'm not sure why we get down the whole header, I think the idea was that it was about as expensive to get the whole header as just a couple of header entries, perhaps this isn't the case. The rescan stuff may be the server sending stuff in an unexpected way, perhaps. On Wed, 2002-03-27 at 18:24, Lea Viljanen wrote: > > The only gripe I have with evolution is the speed > of the IMAP folder handling (i.e Camel). For example, > I have about 830 messages in a folder and the first > open of this folder takes: > - Evo 1.0.2 20 seconds > - Mozilla 7 seconds > > This is a major problem, since I have several > folders with several thousands or so messages. > > I did some sniffing and > > - Mozilla seems to do first just UID FETCH of > the flags and then selective fetch of specific > headers > - Evolution seems to do first UID FETCH on > the flags and size. And then fetch of *all* > the headers. > > And the question is, why is Evolution/Camel > doing it this way and could we get a speed- > tweak option somewhere to reduce the # of > headers transmitted? > > My IMAP folder storage format is MH on the > server, but that shouldn't be a factor here. > > I also have some additional IMAP problems, such > as spurious scanning/fetching of large folders > if a new message arrives suitably or when I move > stuff between folders. But these may also be our > IMAP server problems so I'm not complaining about > those ... yet 8) > > -- > Lea 'LadyBug' Viljanen Insanity is hereditary, > [EMAIL PROTECTED] you get it from your kids > > > > _______________________________________________ > evolution-hackers maillist - [EMAIL PROTECTED] > http://lists.ximian.com/mailman/listinfo/evolution-hackers _______________________________________________ evolution-hackers maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution-hackers
