Message-ID: <5f30e2610608021526g5083268mad6565d7c13877f9@mail.gmail.com>
Date: Wed, 2 Aug 2006 17:26:40 -0500
From: "Jeff Wilson" <jazzbotley@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
MIME-Version: 1.0
Subject: [Bluez-users] nonblocking socket
Reply-To: BlueZ users <bluez-users@lists.sourceforge.net>
Content-Type: text/plain; charset="us-ascii"
Sender: bluez-users-bounces@lists.sourceforge.net
Errors-To: bluez-users-bounces@lists.sourceforge.net

I am using bluez-libs-2.25 on 2.6.11-mh2 to develop BlueZ support for
a multithreaded process.  My BlueZ contribution opens a non-blocking
RFCOMM socket in one thread, and blocking SDP query in another.  So
far, I have RFCOMM support working, and I have also integrated
Bluetooth inquiry and SDP queries.

When I set RFCOMM to nonblocking, the sdp_connect returns an error,
with errno set to EALREADY.  Why does one thread affect the other?

This same SDP query worked fine before I change the RFCOMM to nonblocking.

I can provide hcidump or source code if needed.

    Thanks,
       Jeff

-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users