Re: [Evolution-hackers] Persisting ESource

[Harish Krishnaswamy <kharish novell com>]

On Mon, 2006-07-24 at 14:36 -0700, Scott Herscher wrote:
> Hey all.  I'm trying to add a property to an ESource instance after it
> has been created.  This change doesn't seem to persist at all.  In my
> ECalBackend class, I call e_source_set_property(...).  Looking at the
> code, e_source_set_property() just add the key /val to it's hashtable.
> Where and when does it get written out to disk?  How do I ensure this
> happens?
> 
What is the property you wish to persist ?
Generic properties that need persistence should go into GConf (you can
refer to the schema that defines what are saved).ECalBackend objects
signals the change in property values to ECal objects and changes
to/from GConf are synchronized.

ESource properties specific to remote servers (such as GW) are usually
saved to the server and retrieved every session. 

HTH,
Harish