From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] dbus api
Date: Tue, 29 May 2007 06:08:52 +0200 [thread overview]
Message-ID: <1180411732.21432.119.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <465AF314.5090206@rousse.org>
Hi Alexander,
> I'm working on a C++ library that invokes bluez over dbus. I'm currently
> having some trouble understanding the logic of a local service. Could
> someone explain me the way local services are managed? Like, calling
> RegisterService() of the org.bluez.Database, what does that method do?
> Does it create a new ServiceRecord on hciX? If so, what happens with the
> protocol descriptors of that service record? How can I list all the
> registered services on hciX? I see Add and Update methods for service
> records but no ListServiceRecords()? There is a ListServices() method on
> the manager interface but this interface is just for the /org/bluez
> object path, so this won't give me a list just for hciX. Also, the
> org.bluez.Service interface, does it have anything to do with
> Add/UpdateServiceRecord() methods of the database interface? Can I
> modify the service record (for example the protocol descriptors) of a
> service represented by the org.bluez.Service interface?
a service and a service record are two different things.
The service is something that is BlueZ based. It normally implements one
or more profile specifications and provides a D-Bus interface to use
them.
The service record are SDP records that are mandated by the profile
specification.
You can use both independently. However both are bound to your D-Bus
connection. If you connection dies (meaning your process disconnects)
the service and also the service records will be automatically removed.
> What happened with the RFCOMM API? I agree it wasn't very nice by
> forcing you to open /dev/tty* but it was at least something, now there
> isn't anything dbus based. A RFCOMM API with connect(), disconnect(),
> read() and write() will be just great (all dbus based ofcourse, no
> /dev/tty* stuff :) ).
The RFCOMM API has been moved over to a serial service.
If you don't wanna open /dev/rfcomm* then use Bluetooth RFCOMM sockets
directly. D-Bus is not for transferring data.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-05-29 4:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-28 15:19 [Bluez-devel] dbus api Alexander
2007-05-29 4:08 ` Marcel Holtmann [this message]
2007-05-30 9:14 ` Alexander
2007-05-30 9:36 ` 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=1180411732.21432.119.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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