From: Max Krasnyansky <maxk@qualcomm.com>
To: "Daryl Van Vorst" <daryl@wideray.com>,
"'Marcel Holtmann'" <marcel@rvs.uni-bielefeld.de>
Cc: "'BlueZ Mailing List'" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] RE: Qualification testing - rfcomm
Date: Tue, 22 Jul 2003 09:26:17 -0700 [thread overview]
Message-ID: <5.1.0.14.2.20030722092434.095fc780@unixmail.qualcomm.com> (raw)
In-Reply-To: <001001c347cb$97a39840$1a01010a@baked>
At 09:43 AM 7/11/2003, Daryl Van Vorst wrote:
>Marcel,
>
>You're right that it doesn't check the error code, it just exits. But that
>doesn't explain why it sends 5 frames, waits for 20 seconds, and then sends
>5 more. Shouldn't send block?
Yes it should. But only for SO_SNDTIMEO, which is set to 30 sec by default.
Max
next prev parent reply other threads:[~2003-07-22 16:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 18:16 Qualification testing - rfcomm Daryl Van Vorst
2003-07-08 21:47 ` [Bluez-devel] " James Courtier-Dutton
2003-07-08 23:23 ` Daryl Van Vorst
2003-07-18 19:35 ` James Courtier-Dutton
2003-07-11 8:18 ` [Bluez-devel] " Marcel Holtmann
2003-07-22 16:23 ` Max Krasnyansky
2003-07-22 16:46 ` Marcel Holtmann
2003-07-22 17:40 ` Max Krasnyansky
2003-07-22 19:13 ` Marcel Holtmann
2003-07-22 16:48 ` Daryl Van Vorst
2003-07-22 16:53 ` Marcel Holtmann
2003-07-22 17:01 ` Daryl Van Vorst
2003-07-11 8:55 ` Marcel Holtmann
2003-07-11 16:43 ` Daryl Van Vorst
2003-07-11 19:05 ` [Bluez-devel] " Daryl Van Vorst
2003-07-18 18:53 ` Daryl Van Vorst
2003-07-18 18:58 ` Marcel Holtmann
2003-07-18 19:07 ` Daryl Van Vorst
2003-07-18 19:12 ` Marcel Holtmann
2003-07-18 19:19 ` Daryl Van Vorst
2003-07-22 17:09 ` Max Krasnyansky
2003-07-22 18:13 ` David Woodhouse
2003-07-22 19:43 ` Max Krasnyansky
2003-07-22 16:26 ` Max Krasnyansky [this message]
2003-07-18 19:30 ` [Bluez-devel] " James Courtier-Dutton
2003-07-18 20:25 ` Daryl Van Vorst
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=5.1.0.14.2.20030722092434.095fc780@unixmail.qualcomm.com \
--to=maxk@qualcomm.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=daryl@wideray.com \
--cc=marcel@rvs.uni-bielefeld.de \
/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