http://bugzilla.moblin.org/show_bug.cgi?id=8059 Summary: Session.SetConfig() + remove peer Classification: Moblin Projects Product: SyncEvolution Version: upstream Platform: Netbook OS/Version: Moblin Linux Status: ASSIGNED Severity: normal Priority: P1 Component: *Feature Request AssignedTo: syncevolution(a)lists.intel.com ReportedBy: patrick.ohly(a)intel.com CC: syncevolution(a)lists.intel.com Depends on: 7707 We defined "SetConfig(update=false, {})" so that this removes all properties referenced by the view and those config nodes which become empty because of this. The goal was to use this to remove peers and/or sources. The problem now is that some of the removed properties may still be in use by other peers. Should we redefine the API so that only the unshared properties get removed? Suppose that there is only one peer. Selecting that peer for a session and doing the call above would remove the peer and leave the peer-independent source settings in place. To also get rid of those, we could define that selecting the source set instead of a specific peer and then doing the SetConfig() above really removes the sources. -- 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.