From: Nitin Mahajan <nitinm76@yahoo.com>
To: Marcel Holtmann <marcel@holtmann.org>,
BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] BlueZ APIs
Date: Wed, 29 Aug 2007 04:25:41 -0700 (PDT) [thread overview]
Message-ID: <244253.57477.qm@web50108.mail.re2.yahoo.com> (raw)
HI Marcel!=0A=0AThanks for your inputs, is that possible I can use the Blue=
Z without D-BUS also?=0A=0Aregards=0A=0A-Nitin=0A=0A----- Original Message =
----=0AFrom: Marcel Holtmann <marcel@holtmann.org>=0ATo: Nitin Mahajan <nit=
inm76@yahoo.com>; BlueZ users <bluez-users@lists.sourceforge.net>=0ASent: W=
ednesday, August 29, 2007 3:18:19 PM=0ASubject: Re: [Bluez-users] BlueZ API=
s=0A=0A=0AHi Nitin,=0A=0A> I am new to Bluetooth programming. I have read s=
ome documentation at BlueZ website and the WiKi regarding bluetooth program=
ming. =0A> What I understood is that the latest BlueZ stack has it's interf=
ace as the BlueZ D-BUS API, through which one can avail bluetooth services.=
=0A> =0A> What I wanted to understand that Is there a way I can avail thes=
e services without using D-BUS/ D-BUS API and by directly accessing some Bl=
ueZ API. One way I know is Bluetooth socket programming, but cannot cover e=
ach and every bluetooth functionality. What are the additional set of APIs =
to access bluetooth services. Is there a place where these BlueZ APIS(other=
than BlueZ socket and D-BUS API) are documented?=0A=0Ause the L2CAP and RF=
COMM sockets and the D-Bus API for BlueZ. Everything=0Aelse it not worth us=
ing.=0A=0ARegards=0A=0AMarcel=0A=0ASend instant messages to your online fri=
ends http://uk.messenger.yahoo.com
next reply other threads:[~2007-08-29 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 11:25 Nitin Mahajan [this message]
2007-08-29 13:54 ` [Bluez-users] BlueZ APIs Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2007-09-26 5:08 Nitin Mahajan
2007-09-26 22:12 ` Marcel Holtmann
2007-08-29 8:57 Nitin Mahajan
2007-08-29 9:48 ` Marcel Holtmann
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=244253.57477.qm@web50108.mail.re2.yahoo.com \
--to=nitinm76@yahoo.com \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.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