From: Marcel Holtmann <marcel@holtmann.org>
To: Nitin Mahajan <nitinm76@yahoo.com>,
BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] BlueZ APIs
Date: Wed, 29 Aug 2007 11:48:19 +0200 [thread overview]
Message-ID: <1188380899.6109.35.camel@violet> (raw)
In-Reply-To: <722489.76935.qm@web50107.mail.re2.yahoo.com>
Hi Nitin,
> I am new to Bluetooth programming. I have read some documentation at BlueZ website and the WiKi regarding bluetooth programming.
> What I understood is that the latest BlueZ stack has it's interface as the BlueZ D-BUS API, through which one can avail bluetooth services.
>
> What I wanted to understand that Is there a way I can avail these services without using D-BUS/ D-BUS API and by directly accessing some BlueZ API. One way I know is Bluetooth socket programming, but cannot cover each 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?
use the L2CAP and RFCOMM sockets and the D-Bus API for BlueZ. Everything
else it not worth using.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-08-29 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 8:57 [Bluez-users] BlueZ APIs Nitin Mahajan
2007-08-29 9:48 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-29 11:25 Nitin Mahajan
2007-08-29 13:54 ` Marcel Holtmann
2007-09-26 5:08 Nitin Mahajan
2007-09-26 22:12 ` 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=1188380899.6109.35.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=nitinm76@yahoo.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