From: Till Harbaum <harbaum@beecon.de>
To: Talbi <amine@baracoda.com>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] BlueZ Disconnects
Date: Tue, 3 Aug 2004 12:22:31 +0200 [thread overview]
Message-ID: <200408031222.31152.harbaum@beecon.de> (raw)
In-Reply-To: <200408031214.36250.amine@baracoda.com>
On Tuesday 03 August 2004 12:14, Talbi wrote:
> there is a way using BlueZ to detect a disconnection between my dongle and
> a Bluetooth device.
Sure, it works exaclty like it does with e.g. a lost tcp connection. If you
are using the select, you e.g. get a read event. But the actual read() call
returns with 0 bytes read. You then know, that your l2cap connection is gone.
This should work similar with rfcomm.
Till
--
Dr.-Ing. Till Harbaum Tel.: +49 721 4998963
BeeCon GmbH Fax: +49 721 4998962
Haid-und-Neu Strasse 7, 76131 Karlsruhe Mobil: +49 179 9087904
harbaum@beecon.de http://www.beecon.de
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-08-03 10:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 14:38 [Bluez-devel] IPv6 Bluez and Router Advertissement Jérôme LECOMTE
2004-08-02 18:59 ` Marcel Holtmann
2004-08-02 20:26 ` David Woodhouse
2004-08-03 7:59 ` [Bluez-devel] BlueZ Disconnects Talbi
2004-08-03 8:28 ` David Woodhouse
2004-08-03 10:14 ` Talbi
2004-08-03 10:22 ` Till Harbaum [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=200408031222.31152.harbaum@beecon.de \
--to=harbaum@beecon.de \
--cc=amine@baracoda.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