From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
In-Reply-To: <44DA046D.7020600@pracucci.com>
References: <44DA046D.7020600@pracucci.com>
Date: Wed, 09 Aug 2006 23:53:40 +0200
Message-Id: <1155160420.4492.6.camel@aeonflux.holtmann.net>
Mime-Version: 1.0
Subject: Re: [Bluez-devel] connect() and L2CAP_CONN_TIMEOUT
Reply-To: BlueZ development <bluez-devel@lists.sourceforge.net>
Content-Type: text/plain; charset="us-ascii"
Sender: bluez-devel-bounces@lists.sourceforge.net
Errors-To: bluez-devel-bounces@lists.sourceforge.net

Hi Marco,

> I need to be sure that an SDP connection does not take more than X
> seconds. In order to achieve my goal, I have correctly set the page
> timeout of my local device. However, if I'm right, the page timeout is
> the max time the local Link Manager will wait for a baseband page
> response. But what does it happen if the page request is successfully
> completed and an error occur during the connection to L2CAP remote
> "layer"? Is there a timeout for this? Maybe L2CAP_CONN_TIMEOUT...
> 
> I have posted this message, because practical experiments demonstrate
> that sometimes the sdp_connect() timeout expires after 40 seconds.

run "hcidump -X -V" to check what timeout you really run into.

Regards

Marcel


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel