From: Marcel Holtmann <marcel@holtmann.org>
To: Olivier Le Pogam <olepogam@free.fr>,
BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Blocking connect(AF_BLUETOOTH, SOCK_STREAM, BTPROTO_RFCOMM) => EINPROGRESS
Date: Mon, 22 Oct 2007 11:22:26 +0200 [thread overview]
Message-ID: <1193044946.6184.157.camel@violet> (raw)
In-Reply-To: <000b01c81484$989af5b0$0200a8c0@jester>
Hi Oli,
> 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.
I have no idea what you are trying to achieve here. Anyway, the RFCOMM
socket behaves like every other TCP socket. So in the non-blocking case
apply the same stuff you use when programming TCP.
Regards
Marcel
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2007-10-22 9:22 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 ` [Bluez-devel] Blocking connect(AF_BLUETOOTH, SOCK_STREAM, BTPROTO_RFCOMM) => EINPROGRESS Olivier Le Pogam
2007-10-22 9:22 ` 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=1193044946.6184.157.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=olepogam@free.fr \
/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