RE: [Bluez-devel] Qualification - L2CA_DisconnectCfm

[Marcel Holtmann <marcel@rvs.uni-bielefeld.de>]

Hi Daryl,

> What happens when you close an L2CAP connection?

if you close() the L2CAP connection, we send a L2CAP_DISCONN_REQ and set
a timeout of 5 seconds. In the case of L2CAP_DISCONN_RSP or the timeout,
we close the L2CAP channel.

Max, please correct me if this is wrong, because I am not 100% sure.

> There is a test (see below) where the IUT sends an L2CAP disconnect request
> but the tester ignores it (doesn't send a disconnect response). To pass the
> test we must at least show an "L2CAP_DisconnectCfm" to the application.
> Indicating that a timeout ocurred is optional.

I don't understand why the application needs to now if the L2CAP channel
is correctly disconnected? We close the L2CAP socket and the rest has to
be done by the kernel. If the link is dead and the other side didn't
response, waiting 60 seconds won't help. Or did you see any advantage of
a blocking close()?

Regards

Marcel




-------------------------------------------------------
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