From: "Abraham J. Velez \(EndoraSoft\)" <ajvelez@endorasoft.es>
To: <linux-bluetooth@vger.kernel.org>
Subject: Fw: Question about the connect Function and BlueZ.
Date: Sat, 22 Aug 2009 22:50:05 +0200 [thread overview]
Message-ID: <9DEA418B8D574156A6FD8FE5923922EF@TSESUO> (raw)
Hi Marcel,
Thanks for you answer...
> the problem seems similar or the same to what Nick posted a view weeks
> ago. If you use blocking connect() in one thread the close() in another
> thread will not terminate the connection attempt. As far as I can tell
> this is true and should be fixed. It however works fine if you just
> would use proper non-blocking connect() with a mainloop.
The problem of this method is the control of errors. The call to connect
function is blocking (because we need to
know if the user of the terminal can not connect errno==ECONNREFUSED).
If the connect is not blocking .... i don´t know how evaluate a possible
error. The errno haven´t the error...
(we need to know if the user rejects the connection: In the case of Obex...
the send of the file)
Any Idea?
Thanks in avanced.
Best Regards,
Abraham.
next reply other threads:[~2009-08-22 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-22 20:50 Abraham J. Velez (EndoraSoft) [this message]
2009-08-22 21:20 ` Fw: Question about the connect Function and BlueZ David Sainty
2009-08-24 17:19 ` Abraham J. Velez (EndoraSoft)
2009-08-24 21:19 ` David Sainty
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=9DEA418B8D574156A6FD8FE5923922EF@TSESUO \
--to=ajvelez@endorasoft.es \
--cc=linux-bluetooth@vger.kernel.org \
/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