> Anyways, the idea is that if we make it so that the location of the IMAP > cache is part of the account config rather than being a path that the > imap store creates itself during instantiation, we could more easily > delete the cache when the user deletes his/her account (because the > mailer would know where the cache dir was).
The mailer already can know that. Just call camel_service_get_path() on the CamelImapStore. Everything underneath that directory can be nuked when the account is deleted. > This would also mean that if the hostname of the mail server changes, > the new imap camel-object would also just magically re-use the existing > cache dir rather than starting a whole new one. True. (Could also be dealt with by having the mailer rename the old dir to the new name.) > We'd probably want to use some sort of random string or something (this > sems to be what mozilla does) rather than "[EMAIL PROTECTED]:port" as the > cache dir name too. Sounds like a job for account->uid. -- Dan _______________________________________________ evolution-hackers maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution-hackers
