From: Iain Hibbert <plunky@rya-online.net>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: "linux-bluetooth\@vger\.kernel\.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Implements the OBEX server/SyncML client binding for syncEvolution (http://syncevolution.org/).
Date: Tue, 20 Oct 2009 08:39:10 +0100 (BST) [thread overview]
Message-ID: <1256024351.279827.7068.nullmailer@galant.ukfsn.org> (raw)
In-Reply-To: <1256023119.9142.19.camel@pohly-mobl1.ikn.intel.com>
On Tue, 20 Oct 2009, Patrick Ohly wrote:
> > + 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
next prev parent reply other threads:[~2009-10-20 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 2:58 [PATCH] Implements the OBEX server/SyncML client binding for syncEvolution (http://syncevolution.org/) Forrest Zhao
2009-10-20 7:18 ` Patrick Ohly
2009-10-20 7:39 ` Iain Hibbert [this message]
2009-10-20 9:05 ` Zhao Forrest
2009-10-20 13:18 ` João Paulo Rechi Vita
2009-10-21 1:26 ` Zhao Forrest
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1256024351.279827.7068.nullmailer@galant.ukfsn.org \
--to=plunky@rya-online.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=patrick.ohly@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox