On 2010-01-25, at 19:45 , Lukas Mathis wrote: > > John C. Welch wrote: >>> 3) Implement IMAP well, or at least provide the option to behave properly. >>> (Mulberry is one of the few that do this). So when you have a list of >>> headers in a header view, that's all you download. > > Caio Chassot wrote: >> I think we're going on that direction. > > I think this is (unfortunately) a case where we can't avoid supporting > both aggressive downloading/caching, as well as the behavior John > describes. People use mail differently. A common use case in Europe is > to download mails, hop on a train to a meeting, and work on the mails > while on the train, without Internet connection. It would be > incredibly annoying if that was when you discovered that the > application didn't download message content, or attachments. > > Additionally, I like to have a complete local backup of my Gmail > account, in case Google decides to randomly lock me out. > > There's also the problem that you can't filter on message content > unless you load it.
The original goal is to support full caching. What I was talking about is that we're being smart about download order. Or so seemed to be the consensus on dev. Headers first, messages second, attachments later. And any UI event gets priority. If you select a message whose body has not been downloaded yet, we prioritize it. If you want to check its attachments, they too get to go first. The cache / non-cache battle is fought on another part of that email. _______________________________________________ [email protected] mailing list List help: http://lists.ranchero.com/listinfo.cgi/email-init-ranchero.com
