From: "Daryl Van Vorst" <daryl@wideray.com>
To: "BlueZ Mailing List" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Qualification - L2CA_DisconnectCfm
Date: Fri, 9 May 2003 17:04:39 -0700 [thread overview]
Message-ID: <000a01c31687$c06757a0$1a01010a@baked> (raw)
Max, Marcel,
In order to pass TP/COS/CED/BV-08 we're supposed to be able to indicate tha=
t
there was a timeout waiting for an L2CAP disconnect confirm from the remote
device. I'm waiting for clarification that this is indeed necessary.
The test works like this:
1. We send a disconnect request
2. The tester ignores it.
3. optionally - we resend the disconnect request following a timeout patter=
n
where each retransmission happens after a delay equal to twice the previous
delay.
4. After 60 seconds the channel must be closed - we indicated to the app
that the channel is indeed closed (even though we didn't get a confirmation
from the remote side) and indicate that a timeout ocurred.
I think there's a standard way of doing that sort of thing by setting a
socket option which causes close() to block until things are closed. Not
sure though.
Can we do this with BlueZ?
-Daryl.
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2003-05-10 0:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 0:04 Daryl Van Vorst [this message]
2003-05-12 22:43 ` [Bluez-devel] Qualification - L2CA_DisconnectCfm Daryl Van Vorst
2003-05-12 23:48 ` Marcel Holtmann
2003-05-13 0:11 ` Daryl Van Vorst
2003-05-13 18:00 ` Max Krasnyansky
2003-05-13 22:44 ` Marcel Holtmann
2003-05-13 23:11 ` Max Krasnyansky
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='000a01c31687$c06757a0$1a01010a@baked' \
--to=daryl@wideray.com \
--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