Re: [Bluez-devel] connect() and L2CAP_CONN_TIMEOUT

[Marco Pracucci <development@pracucci.com>]

Hi Marcel,

>>> 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.
>>     

I have resolved the connect() timeout problem, setting two socket
options before connect() system call: SO_SNDTIMEO, SO_RCVTIMEO. Now, it
seems to work fine.

Marco Pracucci


-------------------------------------------------------------------------
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