http://bugzilla.moblin.org/show_bug.cgi?id=5188
--- Comment #6 from pohly <[email protected]> 2009-09-15 01:02:23 --- (In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > > Please also have a look at my "configuration + multiple peers" email on the > > list. The relevant paragraph from that email is the following: > > | Each peer has its own peer-specific settings (credentials, URL and > > | transport) and source-specific settings (URI, sync mode). It might even > > | have more than one way of contacting it (Bluetooth, USB), although how > > | to handle this is a bit uncertain right now. My intention is to deal > > | with this inside the per-server config file instead of creating more > > | config files. > > > > Perhaps my approach is wrong and we really should have one peer > > configuration > > per transport, with shared meta data that is attached to the SyncML device > > ID > > once it is known? > > > > This could add the following files: > > .config/syncevolution/default/.devices/<device ID>/ > > .internal.ini > > sources/addressbook/ > > .internal.ini > > Why can't we extend current configuration to allow mutliple syncURLs per > server > and adding another field activeURL to indicate which transport is actually > used? We could do that. A minor technical detail is that property keys have to be unique, so instead of syncURL = http://server syncURL = bluetooth://mac address we would have to use syncURL = http://server syncBluetooth = mac address:channel or syncURL = http://server syncURL2 = bluetooth://mac address You said that you would prefer syncBluetooth (or something like it), didn't you? Regarding activeURL, I think this is something that our software should figure out automatically depending on which transport is available. Advanced users can force the choice by (temporarily) unsetting all transports except the one they want to be used. > Making per-transport configuration looks not straightforward to me. So you agree with me that one peer configuration per device with multiple transports configured inside it is better? -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
