Re: [Evolution-hackers] imap cache proposal

[Jeffrey Stedfast <fejj ximian com>]

Dan Winship wrote:

> > 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 assumes the object is instantiated which isn't necessarily the case 
(could be disabled).

>  
>
> > 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.)

this gets more complex tho... since you would be moving the object's 
state from one place to another. *much* easier if you didn't have to 
move it at all once the object was instantiated.

>  
>
> > We'd probably want to use some sort of random string or something (this 
> > sems to be what mozilla does) rather than "user hostname:port" as the 
> > cache dir name too.
> >    
>
> Sounds like a job for account->uid.

ah, yea...definetely. :-)

> -- Dan
>
>