Re: [PATCH] Implements the OBEX server/SyncML client binding for syncEvolution (http://syncevolution.org/).

On Tue, 20 Oct 2009, Patrick Ohly wrote:

quoted

+       if (option_syncevolution == TRUE) {
+               services |= OBEX_SYNCEVOLUTION;
+               bluetooth_init(OBEX_SYNCEVOLUTION, "OBEX server for"
+                               " Syncevolution client", NULL,
+                               SYNCEVOLUTION_CHANNEL, TRUE, FALSE, FALSE,
+                               NULL);
+       }
+

Which string is going to appear in the service description (the SDP
part)? This one here? Mentioning "SyncML" would be useful. So I suggest
"OBEX server for SyncML, using SyncEvolution". Leave out the
"SyncEvolution client", because the term client is a) overloaded
(SyncML/OBEX/D-Bus) and b) SyncEvolution could be both client and server
in this context (SAN => SyncML client, SyncML message => SyncML server).

see SDP specification, you can provide ServiceName ("SyncML") and
ProviderName ("SyncEvolution") attributes in the service record..

iain