From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] dbus api
Date: Wed, 30 May 2007 11:36:16 +0200 [thread overview]
Message-ID: <1180517776.21432.182.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <465D4072.6030507@rousse.org>
Hi Alexander,
> where can I read or look for examples of a service? I'm confued, how can
> one make a service available with a name and description?
the bluez-utils source code is full of examples.
> What about listing the currently added local service records? It looks
> like such a method is missing from the API.
And for what do you wanna use that? It is not useful at all.
> If I want to make a rfcomm-based service available on my PC for others,
> than the right way would be to register a service record with a rfcomm
> protocol descriptor and than I should bind listening for new connections
> on rfcomm, right?
Yes.
> What do you mean the RFCOMM API is moved to a service? How can I access
> it? How can I initiate a new rfcomm connection or listen for an incoming
> one?
For servers you wanna use the RFCOMM sockets.
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
prev parent reply other threads:[~2007-05-30 9:36 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
2007-05-30 9:14 ` Alexander
2007-05-30 9:36 ` Marcel Holtmann [this message]
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=1180517776.21432.182.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