--- Comment #5 from pohly <patrick.ohly(a)intel.com> 2011-06-14 12:13:31 UTC ---
(In reply to comment #4)
I guess this requires calling GetConfig for all templates and configs
showing the list of configs/templates...
Just to be clear: do you mean we need to
1. match configuration PeerName to template PeerName if both exist
2. match configuration PeerName to template name if the peerName exists
3. match configuration name to template name (insensitively)
Sounds right to me.
I tried looking this up but my mail archive probably doesn't go
far enough: Do
you remember what was the reason for not doing just #3?
It would have pushed the responsibility of picking a "safe" configuration name
into the UI. It would have to know that a config name like "foo/bar" is invalid
(because the slash would conflict with the mapping to the config files in the
Instead of defining "safe" config names, we picked the approach where the
syncevo-dbus-server sanitizes the chosen config name. That allows changing the
sanitization later on, for example when using a different config storage.
All that the UI needs to know is that a config name may have several aliases
which all map to the same config.
and why not allow
CamelCase config names?
Doesn't work well on the command line - IMHO.
Product: OS Middleware
MeeGo Release: 1.2
Assigned To: patrick.ohly(a)intel.com
Target Build: ---
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.