http://bugzilla.moblin.org/show_bug.cgi?id=5188
--- Comment #5 from Chen Congwu <[email protected]> 2009-09-15 00:24:17 --- (In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #2) > Remember, we are trying to provide a service for very inexperienced users. Agreed. > 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? Making per-transport configuration looks not straightforward to me. -- 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
