From: Marco Pracucci <development@pracucci.com>
To: Bluez Development ML <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] connect() and L2CAP_CONN_TIMEOUT
Date: Wed, 09 Aug 2006 15:51:09 +0000 [thread overview]
Message-ID: <44DA046D.7020600@pracucci.com> (raw)
Hi,
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.
Have you any idea and/or suggestion?
Thanks,
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
next reply other threads:[~2006-08-09 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 15:51 Marco Pracucci [this message]
2006-08-09 21:53 ` [Bluez-devel] connect() and L2CAP_CONN_TIMEOUT Marcel Holtmann
2006-08-10 11:47 ` Marco Pracucci
2006-08-10 16:22 ` Marcel Holtmann
2006-08-10 18:12 ` Marco Pracucci
2006-08-10 19:04 ` Marcel Holtmann
2006-08-23 16:04 ` Marco Pracucci
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=44DA046D.7020600@pracucci.com \
--to=development@pracucci.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).