GNOME Bugzilla – Bug 656473
Store server folder cache in user's cache directory
Last modified: 2011-09-26 10:16:53 UTC
Evolution downloads hundreds of megs of cached message content and dumps them into ~/.local/share/evolution. Then these messages get sucked into my workstation backups. I already have backups done on the server. If they were in ~/.cache/ then they would not be backed up.
Confirming. For example NNTP will use both user's data dir and cache dir, because the backup should contain list of subscribed folders, but messages itself are not that important. On the other hand, if user wishes to copy content locally for offline, then he/she might miss the information in the backup file. Maybe. Anyway, I agree that for providers which have all data stored on the server is better to save local cache into user's cache directory.
Created attachment 197226 [details] [review] eds patch for evolution-data-server; Involves API changes and using of the API for imap, imapx and nntp providers.
Created attachment 197227 [details] [review] evo patch for evolution; Initialize CamelSession's user-cache-dir on creation too.
Created attachment 197228 [details] [review] eex patch for evolution-exchange; Use the cache dir in eex as well...
Created attachment 197229 [details] [review] ema patch for evolution-mapi; ... same as in ema.
Looks awesome! I wonder if it would be worth also adding a migrate_files() method to CamelServiceClass to be called during service_construct(), so providers have a more formal hook to use for migration tasks both now and in the future. Might also prove beneficial to have more centralized control over when file migration occurs. It has in Evolution, at least.
Created commit baabf6b in eds master (3.3.1+) Created commit f579563 in evo master (3.3.1+) Created commit 13201f8 in eex master (3.3.1+) Created commit 5c8a2be in ema master (3.3.1+)