From: "Patryk Zawadzki" <patrys@pld-linux.org>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] What happens with bluetooth when connection is interrupted
Date: Fri, 19 Sep 2008 10:18:55 +0200 [thread overview]
Message-ID: <89b6ba3a0809190118h1b85dcd7y9fc7dcf89fab09ee@mail.gmail.com> (raw)
In-Reply-To: <4f9823290809182356x2ad1386bn3de0ebb6ada66789@mail.gmail.com>
On Fri, Sep 19, 2008 at 8:56 AM, Reto Bachmann <reto.bachmann@gmail.com> wrote:
> So I need to connect the D-Bus signal RemoteDeviceDisconnected to find out
> that I am not connected anymore?
>
> Why shouldn't I poll for a status? Is it just because a signal is sent
> either way or is the status i ask for not the true status?
Because polling is the worst strategy both CPU- and power-wise. It
causes frequent wakeups that waste power and prevent CPUs from
entering a deep idle state. They also generate unnecessary traffic for
the IPC mechanism so if every program decided to poll for something
once a second, services like DBus would likely get hosed.
--
Patryk Zawadzki
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-09-19 8:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 9:42 [Bluez-devel] What happens with bluetooth when connection is interrupted Reto Bachmann
2008-09-18 12:08 ` rakesh agarwal
2008-09-18 17:11 ` Marcel Holtmann
2008-09-19 6:56 ` Reto Bachmann
2008-09-19 8:18 ` Patryk Zawadzki [this message]
2008-09-22 6:08 ` Reto Bachmann
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=89b6ba3a0809190118h1b85dcd7y9fc7dcf89fab09ee@mail.gmail.com \
--to=patrys@pld-linux.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