public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Olivier Le Pogam" <olepogam@free.fr>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Blocking connect(AF_BLUETOOTH, SOCK_STREAM, BTPROTO_RFCOMM) => EINPROGRESS
Date: Mon, 22 Oct 2007 10:21:50 +0200	[thread overview]
Message-ID: <000b01c81484$989af5b0$0200a8c0@jester> (raw)
In-Reply-To: 471B5E66.1030601@cilnu.com

Hi,

I am trying to perform RFCOMM connection to a mobile phone thanks to a 
blocking "connect(AF_BLUETOOTH, SOCK_STREAM, BTPROTO_RFCOMM)" (Blocking is 
the only way for me to get a "Connection Refused" return status !), and if 
the phone is still asking for the authorization when the connect times out, 
the connect and leaves with a EINPROGRESS status.

Could you please tell me :
- If there is a way to extend the blocking "connect" timeout ?
- When a connect exists with a "EINPROGRESS" status, does it make sense to 
try another "connect" on the same socket without doing a complete retry 
(close / socket / bind / connect) ?

Thanks a lot,
Oli 


-------------------------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-10-22  8:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19  4:55 [Bluez-devel] BlueZ integration to LINUX kernel (ARM) Robin Gujjar
2007-10-19 11:35 ` Jon Maber
2007-10-21  7:08   ` Robin Gujjar
2007-10-21 14:12     ` Jon Maber
2007-10-22  8:21       ` Olivier Le Pogam [this message]
2007-10-22  9:22         ` [Bluez-devel] Blocking connect(AF_BLUETOOTH, SOCK_STREAM, BTPROTO_RFCOMM) => EINPROGRESS Marcel Holtmann

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='000b01c81484$989af5b0$0200a8c0@jester' \
    --to=olepogam@free.fr \
    --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