From: "Reto Bachmann" <reto.bachmann@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] What happens with bluetooth when connection is interrupted
Date: Mon, 22 Sep 2008 08:08:34 +0200 [thread overview]
Message-ID: <4f9823290809212308h7ba27f0cr7d4e88c67d38b097@mail.gmail.com> (raw)
In-Reply-To: <89b6ba3a0809190118h1b85dcd7y9fc7dcf89fab09ee@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1629 bytes --]
Hi Patryk,
i see the problems and I will change it. I now made some tests and i found
out that the library waits for a specific time until it sends the signal. I
suppose that in this time it tries to repair the connection.
Is it possible to manage this time period with compiling flags or something?
Thanks,
Reto
2008/9/19 Patryk Zawadzki <patrys@pld-linux.org>
> 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
>
[-- Attachment #1.2: Type: text/html, Size: 2414 bytes --]
[-- Attachment #2: Type: text/plain, Size: 363 bytes --]
-------------------------------------------------------------------------
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=/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-09-22 6:08 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
2008-09-22 6:08 ` Reto Bachmann [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=4f9823290809212308h7ba27f0cr7d4e88c67d38b097@mail.gmail.com \
--to=reto.bachmann@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox