From: Matthew Garrett <mjg59@srcf.ucam.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [Patch] Add dbus method for obtaining RFCOMM channels
Date: Thu, 13 Jul 2006 01:11:01 +0100 [thread overview]
Message-ID: <20060713001101.GA17372@srcf.ucam.org> (raw)
In-Reply-To: <1152747138.17416.10.camel@localhost>
On Thu, Jul 13, 2006 at 01:32:18AM +0200, Marcel Holtmann wrote:
> I would actually prefer not to hand the channel around. We have seen
> devices where the channel changes every time they reboot and so it might
> not be a good idea. I would prefer using a unique ID to identify the
> service.
Ok. Is it possible for a device to have multiple services with the same
UUID? If not, is that a reasonable thing to key it off? I noticed the
list of services in dbus-api.txt, but it currently seems somewhat
smaller than the number of available profiles.
> One of the bigger goals is a working SDP cache for these kind of task
> and the knowledge when to refresh the SDP records for a specific
> service. At the moment it is not fully clear how this can be achieved
> and we might simply have to play with certain ways and see what works
> best in the end.
Is there a practical way of knowing when the device has rebooted? If
not, is it possible to simply check the channel on every connection
attempt? I'm keen on working on this stuff, but my experience of
bluetooth is mostly at the ui level rather than the protocol level. From
my point of view, I just want a good way of providing "Get an RFCOMM
connection to this device" to user applications :)
Thanks,
--
Matthew Garrett | mjg59@srcf.ucam.org
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-07-13 0:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 19:39 [Bluez-devel] [Patch] Add dbus method for obtaining RFCOMM channels Matthew Garrett
2006-07-12 23:32 ` Marcel Holtmann
2006-07-13 0:11 ` Matthew Garrett [this message]
2006-07-17 17:49 ` Matthew Garrett
2006-07-17 18:16 ` Matthew Garrett
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=20060713001101.GA17372@srcf.ucam.org \
--to=mjg59@srcf.ucam.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;
as well as URLs for NNTP newsgroup(s).