http://bugzilla.moblin.org/show_bug.cgi?id=8059
--- Comment #9 from pohly <[email protected]> 2009-11-23 02:37:48 PST --- (In reply to comment #8) > > (In reply to comment #6) > > > For global, context nodes, are they shared and stored in a specific place? > > > > Yes: > > ~/.config/syncevolution/config.ini - global > > default/config.ini - shared sync props > Two configs which use the same shared nodes still load them 2 times, right? I > don't find any code to cache these kind of nodes. Yes. This is what I meant in this comment: http://bugzilla.moblin.org/show_bug.cgi?id=8006 "local sync" - FileConfigTree would be instantiated twice and access the same shared config files without sharing the FileConfigNode instances for them, so that changes made in one instance could overwrite changes made in another. I thought I also had commented on it in the code somewhere, but can't find it right now. This is not a problem right now because we intentionally restrict read/write access to a Session and only one Session is allowed to run at a time. With typical uses, only one SyncContext/Config will be active. Theoretically, a D-Bus user could instantiate a Session, run a sync and then change the config while the sync runs. The outcome of this is undefined. I'm tracking it under "local sync" because in that case we will have to run two sync sessions concurrently, one as client, the other as server. -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
