On Fr, 2011-08-26 at 18:08 +0200, Patrick Ohly wrote:
> I think it should send:
> * deviceName: the vendor/model information if available, otherwise
> the user-configurable device name (can't be empty, because
> traditionally it wasn't describe as optional)
> * templateName: the "templateName" from the template, as it used
> to (see above)
> * peerName: the user-configurable name (optional, old
> syncevo-dbus-servers do not provide it)
>
> The syncevo-dbus-server's use of deviceName needs to be adapted to meet
> this revised definition.
>
> I suspect that the UI picks the first deviceName that it encounters and
> ignores the peerName. Jussi, can you confirm that?
It would make sense, because peerName was indeed not provided by the
syncevolution-dbus-server <= 1.2. Here's what it sends:
dict entry(
string "configName"
string
"_usr_share_syncevolution_templates_clients_phone_nokia.ini"
)
dict entry(
string "description"
string "Template for all Nokia phones which support contacts,
notes and combined tasks+events"
)
dict entry(
string "deviceId"
string "syncevolution-3d99e9ac-646a-491d-b473-1861ccc2de1a"
)
dict entry(
string "deviceName"
string "Nokia N97"
)
dict entry(
string "fingerPrint"
string "Nokia N900,Nokia N85,Nokia 7210c,Nokia N97 mini,Nokia
2630,Nokia 6500 Slide,Nokia 5800 XpressMusic,Nokia"
)
dict entry(
string "remoteIdentifier"
string "PC Suite"
)
dict entry(
string "score"
string "4"
)
dict entry(
string "syncURL"
string "obex-bt://A0:4E:04:1E:AD:30"
)
dict entry(
string "templateName"
string "Nokia"
)
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
