From: sancane <sancane@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Bluez question about new profiles delopment
Date: Mon, 18 Jan 2010 11:12:01 +0100 [thread overview]
Message-ID: <4B5433F1.9090706@gmail.com> (raw)
Hi,
I want to develop a new bluetooth profiles for blueZ basing on my
recently experience gained with my prototype implementation of MCAP &
HDP (http://openhealth.morfeo-project.org). My goal is integrate above
profiles using the BlueZ architecture, but i have some question to do.
* I don't have clear what is the difference between implement a new
bluetooth profile (for example MCAP) like a Service or implement it like
a Plugin. What exactly a plugin is?
I open to any suggestion about the architecture integration of MCAP and
HDP. You can contact with me by email or at irc.freenode.net (i'm sancane).
Any ideas are welcome.
Best regards.
next reply other threads:[~2010-01-18 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 10:12 sancane [this message]
2010-01-26 14:36 ` Bluez question about new profiles delopment Claudio Takahasi
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=4B5433F1.9090706@gmail.com \
--to=sancane@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).