Return-Path: Message-ID: Date: Wed, 17 Oct 2007 09:33:14 +0200 From: "Andrea Galbusera" To: Bluez-users@lists.sourceforge.net MIME-Version: 1.0 Subject: [Bluez-users] concurrent calls to RFCOMM connect() Reply-To: BlueZ users List-Id: BlueZ users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-users-bounces@lists.sourceforge.net Errors-To: bluez-users-bounces@lists.sourceforge.net Hi all, I'm planning to write an application handling communication with four bluetooth devices, each with its own BT address. I was thinking to design it with four parallel threads and use rfcomm sockets API. The common thread function will start connecting to the appropriate remote device by allocating a socket and calling connect(). Do I have to consider any particular syncronization issue between the threads? Is this approach reasonable or not? I found posts in the archives about connect() returning EBUSY. This has to be an error code specific to RFCOMM sockets. When is it supposed to be raised? Is it something I have to take into account in my scenario? TIA Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bluez-users mailing list Bluez-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-users