From: Fabrizio Guglielmino <guglielmino@infitsrl.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] RFCOMM sockets
Date: Thu, 20 Mar 2008 12:22:39 +0100 [thread overview]
Message-ID: <47E248FF.60402@infitsrl.com> (raw)
In-Reply-To: <A6B7F17C-B7E5-4A45-8208-D9C1FBC68C96@holtmann.org>
Hi all,
I have 3 embedded devices with temperature sensor. This devices are
accessed from a pc with linux reading data with rfcomm socket, isn't
need to make sdp query for channel because rfcomm channels are
statically assigned (it's lab equipment).
I need to read the 3 devices almost at same time and I've done a little
C application using GLib IOChannels and non-blocking socket to read
data from the devices. All works fine but if a device it's off the
connection to the others it's slow, my impression is it waits timeout
from the first device.
I can understand why if I have 3 rfcomm connections issued in
non-blocking way these influences each other.
I'm using BlueZ 3.22 on a debian 4.0 whith kernel version 2.6.22
Thanks
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-03-20 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 16:03 [Bluez-devel] I've found a bug in sdp_cstate_get() function 이주영
2008-03-19 16:47 ` Marcel Holtmann
2008-03-20 4:01 ` 이주영
2008-03-20 12:43 ` Marcel Holtmann
2008-03-20 11:22 ` Fabrizio Guglielmino [this message]
2008-03-20 12:45 ` [Bluez-devel] RFCOMM sockets Marcel Holtmann
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=47E248FF.60402@infitsrl.com \
--to=guglielmino@infitsrl.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;
as well as URLs for NNTP newsgroup(s).