From: Herman Meerlo <herman@service2media.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Inquiry and connection through different devices
Date: Mon, 06 Mar 2006 09:07:32 +0100 [thread overview]
Message-ID: <440BEDC4.5040300@service2media.com> (raw)
Hi all,
I am trying out a setup in which one USB dongle constantly performs an
inquiry and another dongle then performs service searches on the found
devices. But this weekend I was wondering whether this is efficient. The
inquiry returns the found devices together with their clock offsets. But
I suppose that this clock offset means nothing to the other dongle. So
is it wise to do this or is it better to let both dongles perform their
own inquiries and determine their own clock offsets?
Regards,
Herman Meerlo
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
reply other threads:[~2006-03-06 8:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=440BEDC4.5040300@service2media.com \
--to=herman@service2media.com \
--cc=bluez-users@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).