From: Marco Pracucci <development@pracucci.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Inquiry cache management (clock offset)
Date: Thu, 21 Dec 2006 15:12:43 +0000 [thread overview]
Message-ID: <458AA46B.5060201@pracucci.com> (raw)
In-Reply-To: <1166705598.9307.7.camel@violet>
Hi Marcel,
> with Bluetooth 1.2 you can even read the local clock and do your
> computation from there. However I doubt that this will give any real
> improvement. Feel free to prove me otherwise, but please make sure that
> your testing is done with real life scenarios. Meaning moving targets.
>
I have just done some simple tests and I have *not* noticed any
significant differences in performance, as you say.
Marco Pracucci
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-12-21 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 17:00 [Bluez-devel] Inquiry cache management (clock offset) Marco Pracucci
2006-12-20 16:23 ` Marcel Holtmann
2006-12-20 17:30 ` Marco Pracucci
2006-12-21 6:26 ` Pierre-Yves Paulus
2006-12-21 12:53 ` Marcel Holtmann
2006-12-21 14:15 ` Cris
2006-12-21 15:12 ` Marco Pracucci [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=458AA46B.5060201@pracucci.com \
--to=development@pracucci.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.