From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Timeouts
Date: Fri, 29 Apr 2005 15:42:23 +0200 [thread overview]
Message-ID: <1114782143.8836.91.camel@pegasus> (raw)
In-Reply-To: <4272363F.30502@futurlink.com>
Hi Pedro,
> I am having some trouble with the timeouts of connections under Bluetooth.
>
> My first concern is the initial connection timeout. I try to send a file
> to a mobile phone using OpenOBEX (I use the BtOBEX_TransportConnect()).
> If the owner of the mobile phone ignores the message that appears in the
> mobile's screen (asking him/her whether to accept the connection), after
> 30 seconds the connection fails with "Resource temporarily unavailable"
> (errno=11). How can I modify this 30 seconds?
you need to integrate a connect timeout (SABM timeout) into the RFCOMM
kernel code.
> I can control the page timeout issuing "hciconfig hci0 pageto 8192",
> that will limit the time for (correct me if I am wrong) completing the
> HCI connection to about 5 seconds. But my problem is at a higher level
> (RFCOMM), since the device is whithin range and the HCI connection is
> done correctly. Is there any specific command in the bluez API to change
> the overall connect() timeout? Or is this a Linux issue (something like
> setsockopt())?
The page timeout is only for the underlaying ACL links. The RFCOMM stuff
is not configurable at the moment.
> The other problem is with the call sdp_service_search_attr_req(). There
> is one mobile that I am testing, that does not always respond (I am
> trying to track down the reason). This call takes about 2 minutes to
> give up so, in the previous scenario, it means that other clients are
> waiting for two minutes, something unacceptable. Is there a way to
> reduce this 2 minutes timeout?
I have no idea. I need the phone to play with it.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-04-29 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 6:00 [Bluez-users] access restrictions after passing PIN Michal Nowikowski
2005-04-29 9:52 ` Marcel Holtmann
2005-04-29 10:06 ` Michal Nowikowski
2005-04-29 10:12 ` Marcel Holtmann
2005-04-29 13:27 ` [Bluez-users] Timeouts Pedro Monjo Florit
2005-04-29 13:42 ` Marcel Holtmann [this message]
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=1114782143.8836.91.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@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