From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: Daryl Van Vorst <daryl@wideray.com>,
"'BlueZ Mailing List'" <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] Qualification - L2CA_DisconnectCfm
Date: 14 May 2003 00:44:13 +0200 [thread overview]
Message-ID: <1052865860.4609.13.camel@pegasus.local> (raw)
In-Reply-To: <5.1.0.14.2.20030513105017.0d234df0@unixmail.qualcomm.com>
Hi Max,
> What we need is SO_LINGER option support. Application doesn't care so much about
> the disconnect itself but it does care if all the data that it had written to a
> socket has been sent.
> i.e.
> connect(sk);
> send(sk, stuff, sizeof(stuff));
> close(sk);
>
> Some apps want close() to sleep until all data has been sent and connection was
> successfully closed.
I never have tought about it before, but SO_LINGER support seems useful.
And with this passing the test will be easy. Did using shutdown() for
disabling sending and receiving works?
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
next prev parent reply other threads:[~2003-05-13 22:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 0:04 [Bluez-devel] Qualification - L2CA_DisconnectCfm Daryl Van Vorst
2003-05-12 22:43 ` 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 [this message]
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=1052865860.4609.13.camel@pegasus.local \
--to=marcel@rvs.uni-bielefeld.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=daryl@wideray.com \
--cc=maxk@qualcomm.com \
/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